Work in a real project · chapter 10 of 17
Testing, verification and evidence
A test examines a specific property. Verification evaluates whether the complete result meets the assignment. Evidence makes the check auditable later.
10.1 · plain explanation
How do we know something works, rather than merely knowing that a command completed?
A test examines a specific property. Verification evaluates whether the complete result meets the assignment. Evidence makes the check auditable later.
Important: A large number of green tests proves nothing they never measured. Connect every check to a concrete risk or completion criterion.
10.2 · building blocks
Three concepts to keep separate
Test
A focused check of a parser, layout, access rule or calculation.
Verification
Compares the user journey and all completion criteria with what is actually running.
Evidence
A report, hash, screenshot or measurement with a timestamp and clear target.
10.3 · method
A practical workflow
- 1Define what can fail.
- 2Run narrow tests while building.
- 3Run an end-to-end check in the correct environment.
- 4Store the decisive result, version and recovery path.
10.4 · concrete example
A bilingual guide
A bilingual guide
How do we know something works, rather than merely knowing that a command completed?
The source check counts chapters and language pairs.
The browser test opens every route and checks H1, canonical, hreflang, schema, overflow and internal links. Production is verified again after publication.
10.5 · try it yourself
Exercise
Choose one completion criterion and write three evidence levels: source check, integration test and live verification.
10.6 · checklist
Before you continue
- Does the test examine the right property?
- Does it run in a relevant environment?
- Can it produce a negative result?
- Can another person understand the evidence later?