Automating Unit Tests
Let’s assume for the time being that the arguments in favor of unit tests and the test-first approach outlined in the introduction are true. One important prerequisite for this approach is the complete automation of the test process. The counter argument most frequently heard concerns the presumably higher initial cost, compared to manual tests. Is there something to this argument?
In conventional test approaches it is assumed that the break-even point between costs and benefits is reached after about 10 test runs ([Kaner 93, p. 196]). This means that automation pays at the latest when you run the automated test more than 10 times in unchanged condition. A rough estimate ...
Get Unit Testing in Java now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.