HTML and CSS Reference
In-Depth Information
In this final chapter we have reviewed some simple guidelines that can help improve
the quality of unit tests. Tests, when done right are a great asset, but bad tests can be
worse than no tests because they introduce a significant overhead in maintenance
and complicate working with code without providing any real value.
The guidelines presented throughout this chapter were divided into three
groups: techniques to improve readability, an important quality of a good unit test;
techniques to generate true unit tests that stay at the unit level; and last, techniques
that help avoid buggy tests.
By working through the example projects in Part III,
Real-World Test-Driven
Development in JavaScript,
and viewing them from a wider angle both in this chapter
and the previous, you should have gained a good understanding of what unit testing
and test-driven development is—and isn't. Now it is up to you. The only way to get
better is to gain as much experience as possible, and I urge you to start practicing
immediately. Create your own learning tests, add features to the example projects
from the topic, or start new projects of your own using TDD. Once you have
grown comfortable within the process that is test-driven development, you won't
go back—you will become a happier and more productive developer. Good luck!
