What is the correct sequence to verify a fix for a reported defect?

• A. Update the user manual and skip regression tests.
• B. Run only unit tests.
• C. Reproduce the original scenario, confirm the fix, and re-run relevant tests to ensure no regression.
• D. Deploy the fix to production without testing.

Answer: (C)

Verifying a defect fix relies on validating the fault under the same conditions, confirming the fix actually resolves it, and ensuring nothing else was broken in the process. Start by reproducing the original scenario to observe the defect again and confirm the exact conditions that triggered it. Next, implement or apply the fix and re-check to make sure the fault no longer appears. Finally, run a relevant set of tests to guard against regressions—this should include tests that cover the area of the change as well as related functionality, so you can spot any new issues that the fix might have introduced.

Updating documentation and skipping regression tests doesn’t provide evidence the defect is resolved in practice, and testing that focuses only on unit tests can miss issues that arise in integration or end-to-end use. Deploying a fix to production without proper testing is unsafe and goes against standard quality practices.