Use Test case for every independently assessed case or checkpoint. Keep batch membership, order, skips, and completion in the authoritative TMS or worksheet. Recorder stores one case reference and one result per recording; it does not know whether the whole batch is complete.

Follow this 10-step routine

1. Select the next case in the external run.
2. Choose Test case, enter its ID, and title the attempt with run/case/attempt/checkpoint.
3. Put the build, role, covered steps, and expected results in Description.
4. Select Start recording, execute only that case or checkpoint, and capture each decisive state.
5. Select Stop → Investigate while the useful path remains in the retained timeline.
6. Verify each criterion against its action, data, and visible result; add source comments.
7. Choose Passed, Failed, or Blocked.
8. Finish Description, review privacy, download or send, and inspect the actual files/destination.
9. Enter the result and evidence reference in the external run manually.
10. Only after that row is complete, select New recording.

Separate Recorder from the run system

Concern	Recorder	External run
Batch membership and order	Not stored	Authoritative
Test-case ID	Typed and stored; no TMS search	Identifies the case and result
Result	Passed, Failed, or Blocked after Stop	Must be entered manually
Attempt/checkpoint	Written in Title and Description	Tracks reruns and multi-recording cases
Evidence	Captured, annotated, downloaded, or sent	Holds the attachment/reference
Defect	Failed/Blocked can optionally create an issue	Keeps the issue link with the result

The locked TMS destination means synchronization is unavailable. It is not proof that the TMS accepted anything.

Choose recording boundaries

Record one short case or checkpoint at a time. A small smoke sequence can share a recording only when every check is identifiable and the complete useful sequence fits the retained interval. The timer can continue after early evidence is evicted.

For a long case, use C1, C2, and covered step numbers. For a rerun, increment A1 to A2 and keep the earlier result. A download retry for the same ready recording is not a new attempt.

Run: R42
Build / environment / role: [fill in]
Case / attempt / checkpoint: TC-142 / A1 / C1
Covered steps and expectations: [fill in]
Result: [Passed / Failed / Blocked]
Observed: [fill in]
Evidence: [NOTES]
Follow-up: [issue or next checkpoint]

Verify each result

For every expected result, confirm the intended Target and captured input, check Payload and Response or the following read when data decides the result, inspect the image with enough context, and use Timeline/Timing when ordering matters. Add a comment with case / step / expected / observed and save it.

Keep positive evidence for a pass. A clean Overview does not pass a case. Give a failure one focused investigation: locate the earliest supported discrepancy, save it, and decide whether the batch can continue. Similar warnings across cases do not establish one cause.

Maintain a useful run index

Case/check	Attempt	Result	Evidence reference	Follow-up
TC-142, steps 1–4	A1 / C1	Failed	Folder plus badge image	QB-17
TC-142, steps 1–4	A2 / C1	Passed	New folder and comparison note	Verification linked
TC-205, setup	A1	Blocked	Summary and access error	Environment owner

List checkpoint gaps and unexecuted cases externally. Recorder cannot infer them from existing recordings.

Deliver, retry, and continue

Insert Notes into Description, review Privacy preview, and select Download report. Confirm completion and open the cited files. Enter the result in the TMS/worksheet and attach them.

Failed or Blocked can create an issue or choose No issue; Passed has no issue action. Report storage is separate. If a file fails, keep the ready session and retry. If TMS attachment fails, keep the folder and retry there. Do not select New recording until the run row points to evidence that opens.

Generated scripts need setup, assertions, and locator review; they do not replace the result or prove batch coverage.

Choose another testing workflow.