Debugging · interview question
If you wrote a test around tracebacks and root cause, what should the test prove first?
Multiple choiceMediumchapter-5-curatedpremiumdebuggingtracebacks-and-root-cause
def line_total(price: float, quantity: int) -> float:
return price * quantity
print(line_total("9.99", 3))Answer and explanation
Correct answer
B. That the rule behaves correctly at the boundary cases the lesson is trying to make explicit.
Why
Good tests make the design safer to change because they lock in the meaningful behavior rather than surface-level implementation details.
Test yourself on Debugging
A free test with instant, explained results. No account needed.
More Debugging questions
- When is logging being used in the wrong way?
- Which move is the best default when logging becomes part of this workflow?
- Which explanation would sound strongest in an interview when discussing logging?
- What assumption should be made explicit when working with logging?
- Which move is the best default when tracebacks and root cause becomes part of this workflow?
- A bug appears around tracebacks and root cause. What is the strongest first debugging move?