Verify, log, prove
Verification items with preconditions, steps and expected result. The verify mode ticks off step by step - and turns it into evidence.
Gerät einschalten
Selbsttest abwarten
Anzeige prüfen: alle Segmente leuchten
Test results that prove nothing
A tick in a list is not evidence.
Passed - against what?
The test ran. Which version of the requirement it ran against, nobody can say afterwards.
No history
The latest result overwrites the previous one. Regression only shows when it hurts.
Failure without consequence
The failed test is in the log. Turning it into a ticket stays manual work.
Verifications without a mandate
What has always been tested keeps being tested - even when no requirement calls for it any more.
Verify mode
The page works with you instead of filing
Preconditions and expected result stay visible while the steps are ticked off one by one. The overall result is derived from them - overridable, because the tester knows more than the rule.
Gerät einschalten
Selbsttest abwarten
Anzeige prüfen: alle Segmente leuchten
BAS-0003 · Abnahme Release 2
Typ Auslieferung · eingefroren am 18.07.2026 · Aufbewahrung bis 2036
248
Anforderungen
163
Prüffälle
410
Verknüpfungen
214
Verifiziert
Der Stand ist unveränderlich. Was heute anders ist, zeigt der Vergleich mit BAS-0002 — dazugekommen, geändert, entfernt.
Runs
Every run is an event, not a field
Result, date, tester, evidence link and optionally the frozen state it was executed against. Runs are never overwritten - the history is the proof.
Failure
A failure becomes a tracked item
A failed run creates a task on the project board in one click - linked to the verification item, pre-filled with title and context. The free-text field remains for external defect databases.
| Unit | Integration | Qualifikation | Abnahme | |
|---|---|---|---|---|
| REQ-0101 | — | |||
| REQ-0102 | — | — | ||
| REQ-0103 | — | — | — | — |
| REQ-0104 |
REQ-0103 hat auf keiner Ebene eine Prüfung — die Lücke steht als Zeile da, nicht als Fußnote.
Questions about verification
For manual verification, reviews, inspections and analyses, yes. Automated test runs stay where they run - importing their results as runs is planned.
Yes, and vice versa. An item covers any number of requirements; a requirement can be backed by several verifications. Both sides show the link.
There was a passed run, but the requirement's content has changed since. The old evidence applies to the old text - which is different from “passed” and different from “unverified”.
Anyone with edit rights for requirements in that project. Rights apply per project and can be tuned via roles and project roles.
Verify and produce the evidence in one go
Try the verify mode with your own verification items.