Test evidence
TodoMVC Demo
PlaywrightGen Demo
Read 2026-11-16 14:45 UTC. It shows the project as it stood at that moment.
Document reference cff2cc253e5c
Approved tests
Requirements
This project has no approved requirements yet, so there is nothing to verify.
Approved tests not linked to a requirement
This test is approved and has run against the real site, so its result is evidence of how the product behaves. It is not linked to an approved requirement, so it does not show that the behaviour is what anyone agreed it should be.
| Test case | Proposed by | Version | Last run | When | Commit |
|---|---|---|---|---|---|
| Edit an existing todo via double-click approved on 2026-11-08 22:33 UTC (the trail no longer names who) |
a person | 1 | passed | 2026-11-16 06:21 UTC | — |
Accepted by
Nobody has accepted this evidence through the link this file came from. Another link to the same evidence may carry acceptances of its own: this file can only speak for the one it was produced from.
How to read this
What it is. Every requirement this project holds that has not been archived -- approved ones and drafts alike -- the approved tests that verify each one, and the result of the last run of each of those tests. A requirement still in draft is included and will read as not verified, because intent nobody has agreed to cannot be counted as covered. It is assembled from stored records only.
What the verdicts mean. Verified means an approved test last ran and passed. Failing means one last ran and did not pass. Not verified means nothing approved covers the requirement, or nothing has run. Verified is not a statement about every acceptance criterion: a test that passed shows what that test checks, and the records do not say which criteria it covers, so each requirement states how many criteria it has for a reader to judge against. No judgement is applied beyond what the records state, and a requirement that nothing has exercised is reported as not verified rather than assumed to be fine.
How each entry came to be here. A person approved the requirement and the test; the approver and date are named against each. Every result was recorded when the test ran, against the approved version it ran. Where an assistant proposed a test, the assistant is named, and a person still approved it.
What this document does not claim. That the names above were identity-checked: a person accepting shared evidence types their own name, and PlaywrightGen records it without verifying who they are. That the evidence is current: each entry states how long ago it was last checked, and nothing here refreshes it. That coverage is complete: it can only report requirements this project has recorded.
Changing it. Requirement, test and run versions cannot be edited after the fact; a change creates a new version. This file is a copy, so treat the document reference above as the way to tell one copy from another.