Verifying a fix under pressure.
WHAT THE PRESSURE PRODUCES
Shortcuts, and fixes that cause further problems.
WHAT TO VERIFY ABOUT THE FIX
That it addresses the actual cause That it resolves the reported symptom That it does not break anything else
WHAT TO TEST SPECIFICALLY
The exact scenario reported Related functionality Anything sharing the affected code
WHAT TO CHECK ABOUT DATA
Whether existing data was affected Whether it needs correcting Whether the correction works
WHY DATA MATTERS MOST
The code fix does not repair what was already damaged.
WHAT TO PREPARE
A way to identify affected records.
WHAT TO TEST ABOUT THE CORRECTION
On a copy, before applying.
WHAT TO VERIFY AFTER DEPLOYMENT
That the problem is actually resolved in production That no new problems appeared
HOW
Monitoring, closely, for a defined period.
WHAT TO ADD AFTERWARDS
A test reproducing the original problem.
WHY
It prevents recurrence, which otherwise happens.
WHAT TO REVIEW
Why testing did not catch it originally.
WHAT TO CHANGE
Whatever allowed it through.
WHAT TO RESIST
Skipping verification because the fix seems obvious.
