Testing · interview question
If reliability stories fails in production, what handling philosophy is strongest?
Multiple choiceHardchapter-9-curatedpremiumtestingreliability-stories
Answer and explanation
Correct answer
B. Fail in a way that preserves the reason, keeps the boundary honest, and avoids hiding the real source of the problem.
Why
Reliable systems preserve context. Silent failure makes the next debugging round slower and riskier.
Test yourself on Testing
A free test with instant, explained results. No account needed.
More Testing questions
- What does a strong engineer do when reasoning through reliability stories code?
- Which naming or modeling choice is strongest for fixtures?
- What production risk should you worry about most if tmp_path and file tests is handled lazily?
- What is the healthiest performance judgment around monkeypatching and mocks?
- What production risk should you worry about most if monkeypatching and mocks is handled lazily?
- Another engineer will maintain this code later. What choice helps the most around reliability stories?