TodayTools

Unit testing flashcards

Fast, honest checks on small pieces of code, with Vitest, Jest and pytest examples from real projects.

Donate
Beginner friendly, starts from zero
Section
How to study
0
Unit testingStart from zero · 1 of 12

What is a unit , in one plain sentence?

A unit is a small piece of code that checks another small piece of code gives the right answer, every time you run it.

Code that checks code.
Show again
12 left
Got it

Tap to turn over. Swipe right if you know it, left to see it again.

All topics

What you will learn

  1. Start from zero

    • What unit tests are and why they exist4 cards
    • Key words: functions and assertions2 cards
    • Runners, bugs and CI in plain words3 cards
    • First win and next steps3 cards

  2. Core basics

    • Why teams test3 cards
    • Runners and project setup6 cards
    • Writing a good test4 cards
    • Matchers, errors and reading failures5 cards

  3. Next steps

    • Test doubles and mocking6 cards
    • Isolation, fixtures and async code5 cards
    • Table-driven tests2 cards
    • Time, randomness and flaky tests4 cards
    • Coverage and snapshots2 cards

  4. Go deeper

    • Strategy: TDD, pyramid and contracts4 cards
    • Designing code for testability4 cards
    • Measuring test quality4 cards
    • Mock lifecycle and hoisting2 cards
    • Runners, environments and speed5 cards

Final test and certificate

10 questions drawn fresh from the whole topic, about 15 minutes. Sign in, score 80% or more and get a free certificate with your name and a public check link anyone can open, such as an employer or a teacher. Not signed in? Try a practice test from the cards.

Take the final test

About these cards

  • Reviewed 26 October 2026
  • CoversVitest 5Jest 30pytest 9Python 3.14Node 24 LTS
How these cards are made

Unit testing at a glance

A unit test is a small piece of code that checks another small piece of code gives the right answer.

Like a smoke alarm for code: quiet when all is fine, loud the moment something breaks.

Words you will meet

Function
A named piece of code that takes inputs and returns an output
Test
Code that runs a function and checks its answer
Assertion
The line that says what the answer must be
Matcher
The kind of check, such as toBe for 'is exactly'
Test runner
The tool that finds tests, runs them and prints a report
Regression
Something that used to work and now does not
Refactor
Tidy code without changing what it does

The steps

  1. 1. Start from zero (12 cards): What a unit test is, why it matters, and the words you need before Core basics.
  2. 2. Core basics (18 cards): Your first real test, assertions that explain failures, and the traps beginners hit.
  3. 3. Next steps (19 cards): Mocks at the right boundary, fixtures, async, timers, coverage and flaky tests.
  4. 4. Go deeper (19 cards): Design for testability, mutation and property testing, mock internals and scale.
All 12 cards in Start from zero
What is a unit test, in one plain sentence?
A unit test is a small piece of code that checks another small piece of code gives the right answer, every time you run it.
Before tests, how did people know a change had not broken anything?
They clicked through the app by hand after every change, which was slow and easy to skip. Bugs slipped out to users, and nobody dared tidy old code.
Where do you already meet the idea of a test in daily life?
When you change a recipe, you taste it before serving. When you fix a bike, you ride it round the block. Apps you use run thousands of such checks before each update.
What is a good everyday picture of a unit test?
A smoke alarm for your code. It stays quiet while everything is fine and goes off loudly the moment something breaks, pointing at the room with the problem.
What do function, input, output and return mean?
A function is a named little machine in code. You give it inputs, it does its job, and it returns an output: add(2, 3) returns 5.
What do test, assertion, matcher, pass and fail mean?
A test runs a function and states what the answer must be; that statement is the assertion. In JavaScript it reads expect(result).toBe(5), where toBe is the matcher. Right answer: pass. Wrong: fail.
What is a test runner, and what are Vitest, Jest and pytest?
A test runner is a tool that finds your tests, runs them all and prints a report. Vitest and Jest are runners for JavaScript and TypeScript; pytest is the runner for Python.
What do bug, regression and refactor mean?
A bug is a mistake in code. A regression is something that used to work and now does not. To refactor is to tidy code without changing what it does.
What are the terminal, a command and CI?
The terminal is a window where you type commands, like npx vitest, to run things. CI (continuous integration) is a robot server that runs all your tests on every change you share.
Your first tiny win: what does this code do?
First comes the function, then the test with a plain name. expect(add(2, 3)).toBe(5) says the answer must be 5; the runner shows pass or fail.
What do you need before you start?
A little of one language, JavaScript or Python: variables and functions are enough. Then a text editor, a terminal, and Node.js or Python installed on your computer.
After this topic, what will you be able to do?
Write and run unit tests in Vitest or pytest, pick the right check for numbers, objects and errors, read a failure report, and keep tests fast and trustworthy.
Unit testing cheatsheet

Vitest and Jest assertions

  • expect(x).toBe(y) Same value or reference (Object.is)
  • expect(x).toEqual(y) Deep equality
  • expect(x).toStrictEqual(y) Deep, plus undefined keys and types
  • expect(n).toBeCloseTo(0.3) Float comparison
  • expect(() => fn()).toThrow(/msg/) Expect an error with message
  • await expect(p).rejects.toThrow() Async error, must await
  • expect.objectContaining({ id }) Partial match
  • test.each(rows)("%s", fn) Table-driven test

Mocking

  • vi.fn().mockResolvedValue(v) Async mock function
  • vi.spyOn(obj, "method") Watch or override one method
  • vi.mock("./mod", () => ({...})) Replace a module, hoisted
  • vi.hoisted(() => ({ m: vi.fn() })) Values usable in vi.mock
  • vi.stubGlobal("fetch", f) Replace a global
  • vi.useFakeTimers() Control timers and Date
  • vi.advanceTimersByTime(300) Move fake time
  • toHaveBeenCalledWith(...) Check call arguments

pytest

  • @pytest.fixture Reusable setup, yield for teardown
  • @pytest.mark.parametrize("a, b", rows) Table of cases
  • with pytest.raises(ValueError, match="x"): Expect an exception
  • monkeypatch.setenv("KEY", "v") Patch for one test
  • tmp_path Temporary folder fixture
  • pytest.approx(0.3) Float comparison
  • capsys.readouterr() Captured stdout and stderr

Command line

  • npx vitest Watch mode
  • npx vitest run -t "coupon" Run once, filter by name
  • npx vitest run --coverage Coverage report
  • npx vitest run --shard=1/4 Split across CI machines
  • pytest -x --lf Stop on first fail, rerun last failures
  • pytest -k "coupon and not slow" Filter by expression
  • pytest -n auto Parallel with pytest-xdist

Config that prevents bugs

  • restoreMocks: true Restore spies before each test
  • unstubGlobals: true Undo vi.stubGlobal after each test
  • coverage.thresholds Fail CI below a floor
  • sequence: { shuffle: true } Expose order dependence
  • onUnhandledRequest: "error" MSW fails on unmocked calls
Donate