The document discusses client-side unit testing. It begins by noting common reasons developers give for not writing tests, such as believing tests are unnecessary or that code is too complex. It then explains the goals of introducing functional testing before unit testing, including automating manual testing and proving functionality from a user perspective without considering internal structure. The document contrasts functional and unit testing, noting unit testing focuses on complete isolation of individual units while functional testing covers most user cases. It argues that as programmers, writers should implement unit tests to ensure high quality code. The remainder covers best practices for unit testing including using a BDD framework, test organization into suites/specs/expectations, and examples of succinct testing syntax.
Related topics: