Get App

Python: Which practice avoids a common mistake with pytest Fixtures and monkeypatch?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with pytest Fixtures and monkeypatch?

  1. Ignore the pytest Fixtures and monkeypatch issue and rely on team discipline instead of clearer APIs or invariants.
  2. Silence the pytest Fixtures and monkeypatch problem by using broad catches, hidden globals, or extra shared mutable state.
  3. Do not patch deep internals or the code under test so aggressively that the test only confirms its own setup.
  4. Prefer the version of pytest Fixtures and monkeypatch that makes behavior less predictable as long as the code still runs.

Hint

Look for the option that protects correctness instead of hiding the problem.

Answer and rationale

Correct answer: C. Do not patch deep internals or the code under test so aggressively that the test only confirms its own setup.

Do not patch deep internals or the code under test so aggressively that the test only confirms its own setup. This is a common failure mode in real Python code and a frequent interview follow-up.

Track: Python