Use Verify fix when a candidate build is ready and the original issue defines what must change. Recorder requires the issue and offers Fixed or Not fixed after Stop. Keep the original evidence unchanged beside the new attempt.

Follow this 10-step path

1. Select Verify fix and choose the issue being verified.
2. Review the fetched Title. If Recorder offers the issue description, choose Add only when appending it will help; it does not stay synchronized.
3. In Description, state the candidate build, original failure point, required criteria, and meaningful differences from the original conditions.
4. Select Start recording and repeat the original setup and trigger.
5. Capture the original failure point and any persistence check, then Stop → Investigate while both remain in the retained timeline.
6. Compare the same logical subject across the action, sent data, returned state, and visible result; do not require identical IDs or encodings.
7. Add comments that pair the original observation with the candidate observation and name the criterion they settle.
8. Choose Fixed only when all required criteria are met; choose Not fixed when a required defect remains.
9. Finish Description, review privacy, and choose Add evidence only or a manual download.
10. Verify the issue comment and attachments, change issue status in the tracker yourself, and only then select New recording.

Understand what Recorder does

Part	Recorder	Tester
Issue	Requires an issue lookup and stores its reference	Confirm it is the defect under test
Description	Can append fetched issue text when you choose Add	State the candidate build, criteria, result, and gaps
Comparison	Shows each recording separately	Keep the old evidence open and compare equivalent subjects/states
Result	Offers Fixed or Not fixed after Stop	Choose from the original acceptance criteria
Send	Offers Add evidence only; the automatic default action is locked	Update issue status or resolution manually
Blocked/inconclusive attempt	Has no matching verification result	Leave result unselected, preserve files, and update manually

The primary send remains disabled until an issue and supported result are selected. Do not choose Not fixed merely to send a blocked or inconclusive attempt.

Define the comparison

Prepare a small map before recording:

Original evidence	Candidate evidence to capture
Meaningful reproduction path	Equivalent setup and trigger, with deviations stated
Important response or state	Same logical property on an equivalent test record
Failure image	Same observation point with enough subject/context
Relevant exception	Whether it recurs and whether the required behavior completes

Recorder’s Environment supplies browser/page context, not the deployed build. Record build, role, data shape, flags, and other application conditions yourself.

For the shared badge example, establish that the badge appears when the card enters Blocked, then verify it clears after leaving. Testing only that the badge is absent could miss a regression where it never appears.

Follow the original discrepancy

1. In Actions, confirm the equivalent Target and prerequisite state.
2. In Payload, check the intended subject and change. A changed contract can be valid; compare meaning, not bytes.
3. In Response or a following read, locate the state that failed originally. Include a reload read when persistence is part of the criterion.
4. In Screenshots & Attachments, verify the expected visible result for the same subject.
5. Use Timeline/Timing for completion and later updates; use Console only when a relevant error changes the interpretation.

The sample archive supplies only failing evidence. A new recording must establish the candidate result.

Decide the verification result

Observation	Recorder result	Next action
Original path completes and every required criterion is met	Fixed	Preserve positive state/data evidence
Required visible, returned, or persistent behavior still fails	Not fixed	Preserve where it first fails and any changed diagnostics
Access, data, build, or another prerequisite prevents the check	Leave unselected	Describe Blocked in Description; download and update manually
Path runs but decisive evidence is unavailable or ambiguous	Leave unselected	Describe Inconclusive and the observation needed next

A corrected response with a wrong screen is Not fixed when the user-visible criterion remains. A corrected screen with required persistence still wrong is also Not fixed. Do not require an old internal field when the agreed behavior no longer depends on it.

Write and send the comparison

Verification: QB-17 / A1 / Fixed
Candidate build / environment: [fill in]
Original evidence: [issue and file reference]
Original steps: [repeated, with deviations]
Expected at failure point: [criterion]
Observed on candidate: [specific result]
Before / after evidence: [NOTES]
Additional checks: [separate results]
Unverified conditions: [list]

In Notes, use View evidence → Add comment → Save comment. State Original → Candidate → criterion settled or unresolved. Insert reviewed Notes into Description and resolve any save error before handoff.

For Fixed or Not fixed, choose Add evidence only. Recorder adds Description and the verification result as issue evidence; it does not close, reopen, or move the issue. The locked default-action choice is not available. Open the issue and confirm text and images, then perform the team’s status change in the tracker.

For blocked or inconclusive attempts, review Privacy preview and Download report. Attach or summarize the result manually without choosing an inaccurate product result. Keep the new folder separate from original evidence.

Issue update, attachment, report storage, and download can fail independently. Retry the failed part; after an unknown timeout, inspect the issue before sending again. Preserve this attempt before another variant and use New recording only after the destination is usable.

Choose another testing workflow.