How do successful agile teams deliver bug-free, maintainable
software--iteration after iteration? The answer is: By seamlessly
combining development and testing. On such teams, the developers write
testable code that enables them to verify it using various types of
automated tests. This approach keeps regressions at bay and prevents
"testing crunches"--which otherwise may occur near the end of an
iteration--from ever happening. Writing testable code, however, is often
difficult, because it requires knowledge and skills that cut across
multiple disciplines.
In Developer Testing, leading test expert and mentor Alexander
Tarlinder presents concise, focused guidance for making new and legacy
code far more testable. Tarlinder helps you answer questions like: When
have I tested this enough? How many tests do I need to write? What
should my tests verify? You'll learn how to design for testability and
utilize techniques like refactoring, dependency breaking, unit testing,
data-driven testing, and test-driven development to achieve the highest
possible confidence in your software. Through practical examples in
Java, C#, Groovy, and Ruby, you'll discover what works--and what
doesn't.
You can quickly begin using Tarlinder's technology-agnostic insights
with most languages and toolsets while not getting buried in specialist
details. The author helps you adapt your current programming style for
testability, make a testing mindset "second nature," improve your code,
and enrich your day-to-day experience as a software professional. With
this guide, you will
- Understand the discipline and vocabulary of testing from the
developer's standpoint
- Base developer tests on well-established testing techniques and best
practices
- Recognize code constructs that impact testability
- Effectively name, organize, and execute unit tests
- Master the essentials of classic and "mockist-style" TDD
- Leverage test doubles with or without mocking frameworks
- Capture the benefits of programming by contract, even without runtime
support for contracts
- Take control of dependencies between classes, components, layers, and
tiers
- Handle combinatorial explosions of test cases, or scenarios requiring
many similar tests
- Manage code duplication when it can't be eliminated
- Actively maintain and improve your test suites
- Perform more advanced tests at the integration, system, and end-to-end
levels
- Develop an understanding for how the organizational context influences
quality assurance
- Establish well-balanced and effective testing strategies suitable for
agile teams
Normal 0 false false false EN-US X-NONE X-NONE
