# Use tests as evidence

Taiga Learning · Worksheet
https://taiga.training/en/lessons/tests-as-evidence/

Use fictional or approved information. Do not put secrets in this worksheet.

## Learning objectives
- Connect each important requirement to a meaningful check.
- Distinguish unit, integration, and end-to-end evidence.
- Detect a test that repeats the same incorrect assumption as the implementation.

## Exercise
Select one generated test. State the requirement it checks. Temporarily introduce the relevant defect in an isolated branch. Confirm that the test fails for the intended reason, then restore the code. Record what the test still does not cover.

## Your response
- Scenario and scope:
- Assumptions and open questions:
- Proposed answer or decision, with reasons:

## Verify your response
| Claim or criterion | Evidence or test | Result or gap | Owner |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |

## Next action
- Action, owner, and date:
- When will you review this response?

## Principle to retain
A passing test is useful only when its assertion would reject a relevant defect.

## Sources
- [Google Engineering Practices: Review tests for useful assertions](https://google.github.io/eng-practices/review/reviewer/looking-for.html)
- [Google Testing Blog: Test scope and feedback](https://testing.googleblog.com/2015/04/just-say-no-to-more-end-to-end-tests.html)

This worksheet supports learning. Completing it does not itself authorize a production change.