Description

Today, it’s widely recommended that developers write automated tests that fail the build when there are regressions. Furthermore, an increasing number of professionals is leaning on a test-first style of programming, using automated tests not for protecting against regression but for aiding them in design, specifying the behavior they expect from code before writing that code, thereby validating a design before verifying its implementation.

where we are today, it’s clear that automated tests have made their way into the mainstream. This is good because without such automated tests, most software projects would be in a far worse situation than they are today. Automated tests improve your productivity and enable you to gain and sustain development speed.

TABLE OF CONTENT

1 Foundations 

• The promise of good tests
• In search of good
• Test doubles

2 Catalog 

• Readability
• Maintainability
• Trustworthiness

3 Diversions 

• Testable design
• Writing tests in other JVM languages
• Speeding up test execution