With Acceptance Test-Driven Development (ATDD), business customers, testers, and developers can collaborate to produce testable requirements that help them build higher quality software more rapidly. However, ATDD is still widely misunderstood by many practitioners. <b><i>ATDD by Example</i></b> is
ATDD by Example: A Practical Guide to Acceptance Test-Driven Development
β Scribed by Markus GΓ€rtner
- Publisher
- Addison-Wesley Professional
- Year
- 2012
- Tongue
- English
- Leaves
- 240
- Series
- Addison-Wesley Signature Series (Beck)
- Edition
- 1
- Category
- Library
No coin nor oath required. For personal study only.
β¦ Synopsis
With Acceptance Test-Driven Development (ATDD), business customers, testers, and developers can collaborate to produce testable requirements that help them build higher quality software more rapidly. However, ATDD is still widely misunderstood by many practitioners. ATDD by Example is the first practical, entry-level, hands-on guide to implementing and successfully applying it.
Β
ATDD pioneer Markus GΓ€rtner walks readers step by step through deriving the right systems from business users, and then implementing fully automated, functional tests that accurately reflect business requirements, are intelligible to stakeholders, and promote more effective development.
Β
Through two end-to-end case studies, GΓ€rtner demonstrates how ATDD can be applied using diverse frameworks and languages. Each case study is accompanied by an extensive set of artifacts, including test automation classes, step definitions, and full sample implementations. These realistic examples illuminate ATDDβs fundamental principles, show how ATDD fits into the broader development process, highlight tips from GΓ€rtnerβs extensive experience, and identify crucial pitfalls to avoid. Readers will learn to
Β
- Master the thought processes associated with successful ATDD implementation
- Use ATDD with Cucumber to describe software in ways businesspeople can understand
- Test web pages using ATDD tools
- Bring ATDD to Java with the FitNesse wiki-based acceptance test framework
- Use examples more effectively in Behavior-Driven Development (BDD)
- Specify software collaboratively through innovative workshops
- Implement more user-friendly and collaborative test automation
- Test more cleanly, listen to test results, and refactor tests for greater value
Β
If youβre a tester, analyst, developer, or project manager, this book offers a concrete foundation for achieving real benefits with ATDD nowβand it will help you reap even more value as you gain experience.
Β
π SIMILAR VOLUMES
In test-driven development, you first write an executable test of what your application code must do. Only then do you write the code itself and, with the test spurring you on, improve your design. In acceptance test-driven development (ATDD), you use the same technique to implement product features
Quite simply, test-driven development is meant to eliminate fear in application development. While some fear is healthy (often viewed as a conscience that tells programmers to "be careful!"), the author believes that byproducts of fear include tentative, grumpy, and uncommunicative programmers who a
Quite simply, test-driven development is meant to eliminate fear in application development. While some fear is healthy (often viewed as a conscience that tells programmers to "be careful!"), the author believes that byproducts of fear include tentative, grumpy, and uncommunicative programmers who a