ShopSpell

Design Driven Testing Test Smarter, Not Harder [Paperback]

$39.99     $49.99    20% Off      (Free Shipping)
100 available
  • Category: Books (Computers)
  • Author:  Stephens, Matt, Rosenberg, Doug
  • Author:  Stephens, Matt, Rosenberg, Doug
  • ISBN-10:  1430229438
  • ISBN-10:  1430229438
  • ISBN-13:  9781430229438
  • ISBN-13:  9781430229438
  • Publisher:  Apress
  • Publisher:  Apress
  • Pages:  368
  • Pages:  368
  • Binding:  Paperback
  • Binding:  Paperback
  • Pub Date:  01-Nov-2010
  • Pub Date:  01-Nov-2010
  • SKU:  1430229438-11-SPRI
  • SKU:  1430229438-11-SPRI
  • Item ID: 100755288
  • List Price: $49.99
  • Seller: ShopSpell
  • Ships in: 5 business days
  • Transit time: Up to 5 business days
  • Delivery by: Jul 03 to Jul 05
  • Notes: Brand New Book. Order Now.

The groundbreaking book Design Driven Testing brings sanity back to the software development process by flipping around the concept of Test Driven Development (TDD)restoring 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 Too Damn Difficult 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, youll 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, test-conscious design patterns), and showing how to create your own test transformation templates in Enterprise Architect.

Here is another ground-breaking book on software development from the team behind Extreme Programming Refactored. Its novel approach of turning test-driven development on its head will attract developers disappointed with the approach of eXtreme programmers.

In this chapter we illustrated how to drive unit tests from a software design, identifying test scenarios in a systematic way that ensures the code is covered in all the right places. We also illustrated the use of stunt services and mock objects to isolate the code being tested; finally, we discussed driving unit tests deeper into algorithmic code that may benefit from finer-grained testing. Is there a way to get 95% of the benefit of the comprehensive unit testing we did il³«
Add Review