Scenarios

Each scenario teaches one testing concept with parallel implementations you can run locally.

integration Assert a 404 JSON error contract
Missing resources return a stable JSON error shape. integration.error-contract
integration GET a resource over HTTP
Hit a real local HTTP handler and assert the JSON body. integration.http-get
performance Smoke-load an HTTP GET
A few virtual users hit GET /items/1; fail if errors or p95 climb. perf.http-smoke-load
performance Microbench a health handler
Burst GET /health and fail if errors or high-percentile latency climb. perf.microbench-handler
security Responses send isolation headers
GET /health must include nosniff and DENY framing headers. security.http-headers
security Markup in a name does not run
Submit a script-like name and assert it is shown as text, not executed. security.xss-escape
unit Assert equality on a pure function
Call a pure function and assert the exact result. unit.assert-equality
unit Specify a behavior with BDD
Write Given–When–Then in the team’s language, then bind those sentences to the SUT. unit.bdd-given-when-then
unit Mock a collaborator
Replace a dependency so the unit under test stays isolated. unit.mock-dependency
unit Parametrize many inputs
Run the same assertion across a table of inputs. unit.parametrize
unit Grow a unit with TDD
Write a failing example first, then the smallest code that passes, then refactor. unit.tdd-red-green
ux Invalid submit shows a message
Submit an empty form and assert the visible validation text. ux.form-validation
ux Click a link and assert the next page
Drive a real browser: click About and check the URL and heading. ux.navigate-and-assert