Cantitate/Preț
Produs

Design Driven Testing: Test Smarter, Not Harder

Autor Matt Stephens, Doug Rosenberg
en Limba Engleză Paperback – 17 sep 2010
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, you’ll 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.
Citește tot Restrânge

Preț: 25166 lei

Preț vechi: 32318 lei
-22%

Puncte Express: 377

Preț estimativ în valută:
4821 5223$ 4135£

Carte indisponibilă temporar

Doresc să fiu notificat când acest titlu va fi disponibil:

Preluare comenzi: 021 569.72.76

Specificații

ISBN-13: 9781430229438
ISBN-10: 1430229438
Pagini: 344
Ilustrații: XVIII, 368 p.
Dimensiuni: 178 x 254 x 20 mm
Greutate: 0.66 kg
Ediția:1st ed.
Editura: Apress
Colecția Apress
Locul publicării:Berkeley, CA, United States

Public țintă

Popular/general

Descriere

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 in this chapter with significantly fewer tests? In the next chapter, we’ll show how to do exactly that with controller tests. As you’ll see, unit tests do have their place, but controller tests can often represent a smarter, more structured approach to application testing. 136 C H A P T E R 6 ? ? ? Conceptual Design and Controller Testing As you saw in Chapter 5, unit testing doesn’t have to involve exhaustively covering every single line of code, or even every single method, with tests. There’s a law of diminishing returns—and increasing difficulty—as you push the code coverage percentile ever higher. By taking a step back and looking at the design on a broader scale, it’s possible to pick out the key areas of code that act as input/output junctures, and focus the tests on those areas.

Cuprins

  1. Somebody Has It Backwards
  2. TDD Using Hello World
  3. “Hello World!” Using DDT
  4. Introducing the Mapplet Project
  5. Detailed Design and Unit Testing
  6. Conceptual Design and Controller Testing
  7. Acceptance Testing: Expanding Use Case Scenarios
  8. Acceptance Testing: Business Requirements
  9. Unit Testing Antipatterns (The “Don’ts”)
  10. Design for Easier Testing
  11. Automated Integration Testing
  12. Unit Testing Algorithms
  13. Alice in Use-Case Land
  14. ’Twas Brillig and the Slithy Tests

Notă biografică

Matt Stephens is a Java developer, project leader, and technical architect with a financial organization based in central London. He's been developing software commercially for over 15 years, and has led many agile projects through successive customer releases. He has spoken at a number of software conferences on object-oriented development topics, and his writing appears regularly in a variety of software journals and websites, including The Register and ObjectiveView. Matt is the co-author of Extreme Programming Refactored: The Case Against XP (Apress, 2003) with Doug Rosenberg, Agile Development with ICONIX Process (Apress, 2005) with Doug Rosenberg and Mark Collins-Cope, and Use Case Driven Object Modeling with UML: Theory and Practice with Doug Rosenberg (Apress, 2007). Catch Matt online at www.softwarereality.com.

Caracteristici

Design Driven Testing brings sanity back to software development by restoring the concept of using testing to verify a design instead of pretending that unit tests are a replacement for design.