The strategies ranged from things like rolling back the change and retesting from scratch, to spot-checking a subset and just shipping it, to writing new targeted unit tests.
Start by clarifying the business impact and urgency, then propose a balanced solution that addresses both immediate customer needs and long-term quality. Rank testing strategies based on their ability to quickly validate the fix while minimizing risk, and emphasize collaboration with stakeholders to align on a phased approach.
Pro tip: Demonstrate ownership by suggesting a short-term hotfix with targeted manual testing, followed by a proper fix with automated tests in the next sprint. This shows you can balance speed and quality while keeping stakeholders informed.
Determine how critical the broken button is: Is it blocking revenue, causing customer complaints, or affecting a small subset? This informs the acceptable risk level.
Rank strategies by speed vs. coverage: manual testing (fastest, least coverage), unit tests (slower, high coverage), integration tests, end-to-end tests, and canary releases.
Suggest an immediate hotfix with quick manual verification to meet the PM's deadline, followed by a proper fix with automated tests to satisfy the EM's quality concerns.
Communicate the plan to both PM and EM, explaining the trade-offs and getting buy-in. Emphasize that the hotfix is temporary and the proper fix will prevent regressions.
Deploy the hotfix, monitor production closely, and schedule the proper fix. Use the incident as a learning opportunity to improve testing processes.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.