June 2019
Intermediate to advanced
192 pages
4h
English
Most tests are an afterthought. A programmer writes hundreds of lines of code to add a new feature to an application, followed by a perfunctory test or two. This “test-later” way of working has several drawbacks.
First, without tests, the programmer receives no feedback while writing the feature. If their approach turns out to be a dead-end, they won’t know it until they’ve finished the entire implementation.
Second, the tests the programmer writes after implementing the feature tend to be unthorough and unimaginative. Typically they confirm that the feature works along the “happy path”—that is, when used exactly as anticipated—rather than revealing potential bugs that might occur under edge case conditions. ...
Read now
Unlock full access