Files
labtimesheet/docs/tests
sechmachine 200a17e5bd
Container / verify (push) Canceled after 4m34s
Container / amd64 (push) Canceled after 0s
Container / arm64 (push) Canceled after 0s
Container / manifest (push) Canceled after 0s
Verify / verify (push) Successful in 8m31s
docs(test): pin registry workflow evidence
2026-08-16 00:28:46 +07:00
..

Test Evidence

TDD is mandatory. Every feature test must have one companion Markdown record in the directory matching its test type:

  • unit/ — isolated state, calculation, and domain behavior.
  • integration/ — PostgreSQL, Flyway, repository, transaction, and module integration.
  • web/ — MockMvc, Thymeleaf, validation, and security behavior.
  • e2e/ — cross-module, browser, or full user journeys.

Copy that directory's _TEMPLATE.md and keep every heading. One evidence file may cover a cohesive parameterized scenario set, but it must name every requirement and scenario ID it protects.

An evidence record is complete only when it contains the observed RED failure, the observed GREEN result, the affected-suite result, and honest external-test boundaries. Commands and relevant output are copied exactly; prose such as "passed locally" is not evidence.