Practice question · Multiple choice
A test suite runs in four hours and developers stop running it before pushing. What has the suite become?
Hints
- Ask when a bug is cheapest to fix, and when this suite would find it.
- A perfect test nobody runs catches how many bugs?
Show the answer
C. Nearly worthless, since a test that is not run catches nothing
Why
Feedback that arrives after you have moved on is barely feedback, and a suite people skip catches nothing at all. That is why fast unit tests are separated from slow integration ones, and why suite runtime is treated as a first-class engineering concern rather than an inconvenience.
Practise Testing Larger Behaviours
The app has 6 more questions on this lesson, and keeps your place in the course. Computer Science I is free to start.
More questions on Testing Larger Behaviours
- Sort each claim by whether a coverage report can actually support it.
- Every unit test in a project passes. Select every kind of defect that could still be present.
- Test-driven development requires the new test to FAIL before any code is written. Why is that step not a…
- A test suite can execute every line of a function and still miss the input that breaks it.