March 2015
Intermediate to advanced
236 pages
5h 26m
English
You can avoid many of the pitfalls that unit testers often drop into by following the FIRST principles of unit testing:
[F]ast
[I]solated
[R]epeatable
[S]elf-validating
[T]imely
The word first itself has significant meaning in the context of unit testing. Right now, you’re probably writing your code first, then writing unit tests after the fact. But, perhaps surprisingly, you can get different and better results if you write the unit tests before you write the corresponding code. A host of folks practice the discipline known as test-driven development (TDD). The sole delineation between plain ol’ unit testing (POUT) and TDD is that in TDD, the tests come first. Check out Chapter 12, Test-Driven ...
Read now
Unlock full access