Test cases and runs

Who can use it: QA writes and runs test cases. Project Managers approve test cases, can run them, and verify results. Everyone, clients included, sees test cases and results.

Test cases prove the acceptance criteria. Each test case checks one criterion, and every run keeps its screenshots as evidence.

Use case

As soon as REQ-4’s requirement is signed off, Lena writes three test cases, one per criterion, while Arjun is still on the spec. Ravi approves them. When T2 is done, Lena runs TC3 (“Unavailable items listed with a note”) and attaches screenshots of the cart. The first run fails: the note is missing. Arjun fixes it, Lena runs it again and it passes, and Ravi verifies the run. All three pass, so REQ-4 is Validated.

One test case per criterion

flowchart LR
    A1["AC1"] --> TC1["TC1 · History shows 20, newest first"]
    A2["AC2"] --> TC2["TC2 · Available items reach the cart"]
    A3["AC3"] --> TC3["TC3 · Unavailable items noted"]

Write a test case

stateDiagram-v2
    [*] --> Draft
    Draft --> InReview: QA submits
    InReview --> Approved: PM approves
    InReview --> Draft: PM requests changes
    Approved --> Draft: QA reopens
    state "In review" as InReview

1. Open the feature’s Test Cases tab and select New test case.
2. Pick the acceptance criterion it checks.
3. Write the title, preconditions, steps and expected result.
4. Submit it. A Project Manager approves it or requests changes.

Run it

stateDiagram-v2
    [*] --> Running: Start a run
    Running --> Failed: Submit FAIL
    Running --> Awaiting: Submit PASS
    Awaiting --> Passed: PM verifies
    Awaiting --> Rejected: PM rejects
    Failed --> [*]: Fix, then new run
    Rejected --> [*]: Fix, then new run
    state "In progress" as Running
    state "Awaiting verification" as Awaiting

1. Start a run on an approved test case.
2. Follow the steps and attach screenshots as evidence, with a caption on each.
3. Submit the outcome: pass or fail, with notes.
4. A Project Manager verifies a pass, or rejects it with a note. A failed run needs no verification.

Note

Every run is kept, so you can see the history of attempts. The test case’s result is its latest run. After a fail or a rejection, fix the issue and start a new run.

Validation

When every acceptance criterion is covered by approved test cases and all of them have passed, the feature becomes Validated and goes to the client for acceptance. From then on its tasks and test cases are read-only.

All test cases in one place

Test Cases in the project lists every test case. Filter by feature, status and result, and open one to see its steps and runs.