Testing · interview question
What is the clearest sign that code around monkeypatching and mocks should be refactored?
Multiple choiceMediumchapter-9-curatedpremiumtestingmonkeypatching-and-mocks
Answer and explanation
Correct answer
A. When the rule is no longer easy to trace, explain, or change without breaking nearby behavior.
Why
A refactor is justified when the code stops communicating its intent. Mock or monkeypatch external systems when the goal is to isolate the rule under test from I/O side effects.
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?