Testing · interview question
A bug appears around boundary and failure tests. What is the strongest first debugging move?
Multiple choiceHardchapter-9-curatedpremiumtestingboundary-and-failure-tests
def test_rejects_zero_quantity() -> None:
with pytest.raises(ValueError):
OrderLine(sku="SKU-1", quantity=0)Answer and explanation
Correct answer
C. 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. Only testing the happy path makes the suite optimistic in exactly the places production is pessimistic.
Test yourself on Testing
A free test with instant, explained results. No account needed.
More Testing questions
- Which option treats api contract testing as an engineering policy decision instead of a syntax trick?
- When is api contract testing being used in the wrong way?
- Which option treats basic pytest assertions as an engineering policy decision instead of a syntax trick?
- Which response shows the healthiest evidence-first mindset around basic pytest assertions?
- What production risk should you worry about most if boundary and failure tests is handled lazily?
- What kind of contract clarity matters most for boundary and failure tests?