Reference · 15 terms
Glossary
Every short form used across the series. Inside a lesson, hover or tap any dotted term to see the same entry in place.
Testing
- arrange-act-assertArrange, act, assert
- The three parts of a clear test: set up, do the thing, check the result.Lesson 1 →
- contract testContract test
- A test that checks two parts of a system agree on the shape of their messages.Lesson 3 →
- fakeFake
- A simple working replacement, such as an in-memory database.Lesson 1 →
- fake timersFake timers
- A test tool that controls time, so timeouts run instantly and predictably.Lesson 1 →
- flaky testFlaky test
- A test that sometimes passes and sometimes fails without any code change.Lesson 4 →
- mockMock
- A test double that also records how it was called, so the test can check the calls.Lesson 1 →
- MSWMSW (Mock Service Worker)
- A tool that fakes network responses at the request level, so your code makes real fetch calls in tests.Lesson 2 →
- mutation testingMutation testing
- Make small deliberate bugs in the code and check that the tests catch them.Lesson 5 →
- property-based testingProperty-based testing
- Check that a rule holds for many generated inputs, and shrink a failing input to a small example.Lesson 5 →
- spySpy
- A wrapper that records calls to a real function while still running it.Lesson 1 →
- stubStub
- A test double that returns fixed answers.Lesson 1 →
- TDDTDD (test-driven development)
- Write a failing test, make it pass, then clean up the code. Repeat in small steps.Lesson 5 →
- test pyramidTest pyramid
- A model that suggests many fast unit tests, fewer integration tests and few end-to-end tests. The trophy and honeycomb are alternative models.Lesson 0 →
- Testing LibraryTesting Library
- UI testing tools that find elements the way users do: by role, label and text.Lesson 2 →
- trace viewerPlaywright trace
- A recording of a test run with snapshots, network and console, used to debug failures.Lesson 4 →