Testing · interview question
Another engineer will maintain this code later. What choice helps the most around monkeypatching and mocks?
Multiple choiceMediumchapter-9-curatedpremiumtestingmonkeypatching-and-mocks
Answer and explanation
Correct answer
B. Make the rule obvious in names, flow, and boundaries so the next reader does not have to reverse-engineer your intent.
Why
Maintainability comes from explicit intent. This is a classic interview seam question because it reveals whether you understand what the test is for.
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?