Testing · interview question
A bug appears around monkeypatching and mocks. What is the strongest first debugging move?
Multiple choiceMediumchapter-9-curatedpremiumtestingmonkeypatching-and-mocks
def test_reads_env(monkeypatch) -> None:
monkeypatch.setenv("ORDER_OPS_MODE", "test")
assert load_mode() == "test"Answer and explanation
Correct answer
A. Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.
Why
That approach is reliable because it creates evidence. If you mock the behavior you are trying to verify, the test mostly confirms your own setup.
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?