Define the incorrect behavior

Describe the gap between expected and actual behavior using a specific input and environment. Clarify ambiguous requirements before choosing an implementation. A feature request changes the agreed behavior; a defect report says the current system fails to meet it. Teams need that distinction when prioritizing work.

Illustrative scenario: a date filter excludes records created on the final selected day. Establish whether the product promises inclusive calendar days and which timezone applies. A screenshot suggests the symptom, while a small dataset around midnight provides the evidence needed to reproduce it.

Repair the cause with a focused change

Trace the failure to a concrete condition, such as an exclusive timestamp boundary or missing timezone conversion. Change the narrowest responsible layer. Avoid broad cleanup while diagnosing the defect, because additional transformations make it harder to identify which change actually corrected the behavior.

Add a regression check that demonstrates the original failure. For the date filter, include the start boundary, end boundary, and an adjacent excluded record. Inspect the proposed patch for changed defaults or altered API contracts that would require a separate product decision.

Verify the fix where it matters

Run the focused regression test and relevant integration checks using the supported environment. If the bug depends on deployed configuration, verify that configuration explicitly. A local pass cannot prove a production-only timezone, permission, or concurrency problem is resolved without representative conditions.

Document the cause, changed behavior, verification, and rollout considerations. For a data corruption defect, repairing the code and repairing existing records are separate tasks. Decide whether historical data needs reconciliation, who approves that operation, and how its result will be checked before calling the incident resolved.

Working sheet

Artifacts of a verifiable bug fix
StageUseful artifactAvoid
ReportExact input and expected resultOnly saying it is broken
DiagnosisEvidence supporting one causeUnverified explanation
PatchSmall relevant diffUnrelated rewrite
VerificationRegression and adjacent-case resultsOnly checking the happy path
Download this worksheet (CSV)

Questions about what is a bug fix, and how do you verify one?

Is refactoring a bug fix?

Refactoring preserves intended external behavior. A bug fix intentionally corrects behavior; keep the distinction visible in the change.

Does every bug need a large test suite?

Use verification proportional to the affected behavior and risk. A focused regression test is often more valuable than many unrelated checks.

How should I use the working sheet?

Download the CSV and replace the sample rows with evidence from your repository. Record a clear acceptance check and an owner for each item. Keep unresolved assumptions visible rather than treating the example as a completed assessment.

Sources and further reading

Examples are illustrative. They are not customer results, security guarantees, or a substitute for checking the documentation for your installed version.

Make the next change verifiable.

Getzilla is an open source workflow for changes to existing repositories. Inspect the project, define acceptance checks, and keep independent review in the loop.

See the repository workflow See current access and pricing