Testing · interview question
Which move is the best default when api contract testing becomes part of this workflow?
Multiple choiceHardchapter-13-curatedpremiumtestingapi-contract-testing
Answer and explanation
Correct answer
B. Use boundary tests to prove routing, validation, status codes, and serialization rather than trusting the framework blindly.
Why
Use boundary tests to prove routing, validation, status codes, and serialization rather than trusting the framework blindly. That is the stronger engineering move because interviewers like candidates who know which parts of the stack deserve their own testing seam. Assuming the framework will do the right thing without verification leaves the contract under-proven.
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?