Testing Architecture Lab
See what each test can detect, and just as importantly, what it cannot prove.
Browser-local learning exercise. All scenarios, costs and receipts are synthetic. No real model, API or service is being evaluated.
1. Choose your system
Different architectures require different test boundaries. The five nodes below are a teaching map, not a claim that a live stack has been tested.
2. Select a testing layer
3. Inspect its responsibility
Interpretation: tests offer evidence at a declared scope. Neither a green badge nor an assertion in a diagram is proof that a real system passed.
4. Make a test decision
Select a layer above, predict where the fault should first be found, then check your answer.
No answer checked yet.