The groundbreaking book Design Driven Testing brings sanity back to the software development process by flipping around the concept of Test Driven Development (TDD)arestoring the concept of using testing to verify a design instead of pretending that unit tests are a replacement for design. Anyone who feels that TDD is aToo Damn Difficulta will appreciate this book. Design Driven Testing shows that, by combining a forward-thinking development process with cutting-edge automation, testing can be a finely targeted, business-driven, rewarding effort. In other words, youall learn how to test smarter, not harder. Applies a feedback-driven approach to each stage of the project lifecycle. Illustrates a lightweight and effective approach using a core subset of UML. Follows a real-life example project using Java and Flex/ActionScript. Presents bonus chapters for advanced DDTers covering unit-test antipatterns (and their opposite, atest-consciousa design patterns), and showing how to create your own test transformation templates in Enterprise Architect. What youall learn Create unit and behavioral tests using JUnit, NUnit, FlexUnit. Generate acceptance tests for all usage paths through use case thread expansion. Generate requirement tests for functional requirements. Run complex acceptance tests across the enterprise. Isolate individual control points for self-contained unit/behavioral tests. Apply behavior-driven development frameworks like JBehave and NBehave Who this book is for Design Driven Testing should appeal to developers, project managers, testers, business analysts, architectsain fact, anyone who builds software that needs to be tested. While equally applicable on both large and small projects, Design Driven Testing is especially helpful to those developers who need to verify their software against formal requirements. Such developers will benefit greatly from the rational and disciplined approach espoused by the authors. Table of Contents Somebody Has It Backwards TDD Using Hello World aHello World!a Using DDT Introducing the Mapplet Project Detailed Design and Unit Testing Conceptual Design and Controller Testing Acceptance Testing: Expanding Use Case Scenarios Acceptance Testing: Business Requirements Unit Testing Antipatterns (The aDonatsa) Design for Easier Testing Automated Integration Testing Unit Testing Algorithms Alice in Use-Case Land aTwas Brillig and the Slithy Tests(and how do we deal with that when it happens) And then keep on asking, what else happens? until you cana#39;t think of any more Alternate Courses. ... Step 7: Create unit test cases from your sequence diagram, and cherry-pick the non- redundant ones. ... 1Actually, just to see if youa#39;re awake (and to show you why we put requirements onto robustness diagrams), we forgot one, as youa#39;ll see in a few pages.
|Title||:||Design Driven Testing|
|Author||:||Matt Stephens, Doug Rosenberg|
|Publisher||:||Apress - 2010-09-16|