One person says Export works and another says the control is disabled. Their starting conditions differ. Write both in the test matrix so someone else can repeat the comparison.

Hold the action steady and change the condition

For this fictional test, check the same Export control with a sample file open and with no file open. Write down the app version and sample file first. The expectations below are sample requirements to verify.

| ID | Condition | Expected | Status | Evidence |
| --- | --- | --- | --- | --- |
| M-01 | Sample file open | Export available | Pending | — |
| M-02 | No file open | Export unavailable | Pending | — |

M-01 expects Export available with a file open and M-02 expects it unavailable with no file open.

Illustrated test plan. Both rows begin as Pending.

Fill the result after the check

Record the observed behavior, Pass, Fail or Blocked, and an evidence reference. If Export behaves differently, keep the original expectation and write down what happened. If you cannot create a test condition, mark the row Blocked and say why.

The result columns keep observed status and an evidence reference separate from the original expectation.

Illustrated recording layout. Fill results after running the check.

Have someone else read one row and reproduce its starting state. GitHub Flavored Markdown table syntax.