Use the original customer reproduction as the acceptance test for a fix. Driver can compare the change with the failing path and find relevant tests; your team runs those checks against the intended build.
Compare the fix with the failure
- Give Driver the original support ticket, linked engineering issue, exact reproduction, and expected result. Include the reviewed handoff so the investigation has facts gathered in other people’s private conversations.
- Select the before and after branches or supply the fix diff. Ask: “Does this change address the reported reproduction? Cite the condition that failed before, the changed behavior, and the test that checks it. List the remaining assumptions.”
- Ask for checks covering the reported input, a nearby supported case, and an unchanged case. Include configuration, permissions, and data-shape differences that matter to this customer.
Run and record the verification
Run the reproduction and proposed checks in your test environment. For the illustrative webhook case, this means checking that HTTP 429 schedules a retry after Retry-After, that HTTP 500 still retries, and that HTTP 400 follows the agreed policy.
Record the following on the engineering issue and link the original support ticket:
| Record | What to include |
|---|---|
| Build and environment | Exact tested revision, environment, and relevant configuration. |
| Reproduction result | Steps, input, expected result, observed result, and test output. |
| Regression checks | Other cases run, results, and any checks still outstanding. |
| Remaining failure | The condition still failing and the evidence needed to investigate it. |
Give Driver those results if you need help explaining a remaining discrepancy. Driver reading the code does not execute the reproduction in your environment.
Pass the result to support
| Role | Responsibility |
|---|---|
| QA or the verifying engineer | Establish whether the intended build passes the reproduction and record the evidence. |
| Engineering or the release owner | Confirm the rollout state and which customer environments have the fix. |
| Support | Use the verification and rollout facts to update the customer and resolve or reopen the Jira ticket. |
Verification on a test build and availability to the customer are separate facts. Closing a Driver investigation records completion of your investigation work; ticket resolution follows your Jira workflow.