Use Driver to turn a release’s changed behavior into a regression checklist with source references and test gaps.
Choose the source revisions
Use this procedure whenever a guide compares a release, fix, or proposed change:
- Name the codebase and available branches. Ask Driver to list the branches it can read for that codebase. In an MCP-connected coding assistant, ask the assistant to use
get_codebase_namesandget_branchesto discover them. - Map versions to source. Ask the release owner which branches represent the before and after versions. For example, if both are available, use
payments, branchrelease/4.2, as the before source andpayments, branchrelease/4.3, as the after source. These are example branch names; replace them with your actual branches. - Supply the change when needed. Paste the relevant diff or changed source into the conversation for a proposed change, an unavailable branch, or an exact historical revision. Label its codebase, base revision, and proposed revision. A pull-request URL or release label by itself does not supply that diff, and connected branches do not include your local uncommitted edits.
- Check what Driver used. Ask the answer to state the codebase and branch for each source citation and identify any supplied diff separately. If a branch has moved since the candidate was built, supply the candidate’s exact change instead. Prepared maps, relationships, and history require Advanced context ready for the selected branch.
For a comparison in your coding assistant, the equivalent source calls use branch_name on each read or search. The MCP reference lists the parameters.
Build and run the checklist
- Start a Driver conversation with the selected codebase, branch, and release diff. Ask: “For these webhook retry changes, identify changed behavior, callers, existing tests, and missing checks. Give each proposed test a failure condition and a source reference.”
- Ask Driver to trace callers and tests. With prepared Advanced context, it can use relationships and change impact to find candidates. Open the cited tests and check what they assert.
- Add known integration conditions to the request: configuration, permissions, external API responses, and data shapes. Ask Driver to separate checks established by source from checks that need an environment or service owner.
- Review the checklist with the release owner. Your team runs the tests and manual checks, then records the candidate revision, environment, result, and unresolved failures in the release issue.
- Repeat the assessment when the candidate changes, using the updated diff and branch evidence.
For a retry-policy change, the checklist might include an HTTP 429 response with Retry-After, an existing HTTP 500 retry, and a non-retryable HTTP 400 response. Those are illustrative checks; the intended policy and cited implementation determine the checks for your release.