Most Helpful Customer Reviews
9 of 9 people found the following review helpful:
4.0 out of 5 stars
Eye opener, September 22, 2010
This review is from: Design Driven Testing: Test Smarter, Not Harder (Paperback)
'Design Driven Testing: Test Smarter, Not Harder' is the second book that I've read by authors Doug Rosenberg and Matt Stephens, the other being 'Use Case Driven
Object Modelling with UML Theory and Practice'. Once again I've been impressed, not only by the content but also, by the manner in which concepts are presented. I have a technical background and spend a considerable amount of time reading journals, blogs, articles and books and I especially enjoy it when the author screams out with passion for his/her subject, as in this case.
Before reading this book I'd not heard too much about DDT and even now it doesn't seem to be generating a huge amount of noise. I think this is maybe because a lot of people and organisations have spent vast amounts of time, money and hard effort investing in TDD.
I've been fortunate to have used TDD on many projects and it never surprises me the number of times when 'TDD' projects are not actually 'TDD'. From a high-level it seems really simple but then again simple things are not always what they seem.
By reading the accounts of Rosenberg and Stephens it's amazing how much one can learn not just about DDT but also TDD. It was also fascinating to learn that a lot of things I've done in the past have been very compatible with the DDT approach, such as robustness analysis and testing `hot-spots'.
I'm not sure if I'll be making the move to a pure DDT approach, but nonetheless it's shown flaws in past TDD projects that I've been part of (e.g. chasing code coverage, lack of design and not thinking deeply about acceptance testing).
The book is a good read and I appreciated the examples and simple concepts such as top 10's. I highly recommend the book even if you're not likely to use DDT because, like me, it's made me think long and hard about TDD and how to get the most out of it.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
4 of 4 people found the following review helpful:
5.0 out of 5 stars
Be smart about your testing, October 3, 2010
This review is from: Design Driven Testing: Test Smarter, Not Harder (Paperback)
Summary:
In software development there is no shortage of methodologies. A seasoned software development team will be careful not to plunge headlong into a particular methodology without properly understanding its strengths and weaknesses. As the proverb says "A person seems right until someone comes forward and questions him." This book provides insight into challenges you may face with a bottom up approach (TDD in particular) and offers a top down approach (the reverse of TDD, or DDT).
Audience:
This book will prove useful to several audiences - managers, architects, analysts, developers and testers. Software development isn't about one role (for example testing) dominating the life cycle - instead it is an ongoing collaborative approach. This is where design and modeling can help to transfer the right requirements to classes and into code. The design drives test cases naturally.
Likes and Dislikes:
The conversational style of writing pulls the reader into the discussion around challenges with proper testing of a real application. If you already understand the benefits of software modeling, you will quickly appreciate how your knowledge can help with smarter software testing. The authors are not advocating an either/or approach between TDD and DDT. Both can coexist but TDD has some blind spots to be aware of. Those who use Enterprise Architect as their modeling tool will be pleased to find several useful screenshots and examples included.
Those who have read and benefited from previous books by the authors will find some of the earlier information repetitive. Thankfully the authors point readers to their other references and quickly move on.
Level of experience required:
Even though the focus of this book is on testing, the ideas run much deeper and complement other books on Domain Modeling by the authors. This is really a book that will help a software team prepare for testing in a well-rounded manner. All levels of experience should read and benefit from such a book.
Recommendation:
This book is a great reminder to take a step back and examine what you are trying to accomplish in a software project. Developing aimless test methods without knowing the bigger picture can potentially lead to wasted time - something no one can afford. Be smart, test the right things. Abstraction and iteration work so use them. I heartily recommend this book for those looking to test software projects using a proven, team oriented, common sense approach.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
4 of 4 people found the following review helpful:
4.0 out of 5 stars
Highly Recommended, September 26, 2010
This review is from: Design Driven Testing: Test Smarter, Not Harder (Paperback)
For those who couldn't believe that it was possible to have upfront analysis and design in an agile, test driven mindset (acceptance testing included), this book shows exactly how to do it, step by step.
Doug Rosenberg and Matt Stephens introduce us DDT, Design Driven Testing, a broader approach than TDD (that is presented at the beginning of the book to show the differences). I liked very much the Chapters about design-oriented testing, with controller and unit tests, and analysis-oriented testing, that presents customers (generally forgotten tests), business analysts and QA tests.
But the authors really deliver what they promise at the subtitle "Test Smarter, Not Harder" when they present the Controller tests, which cover more functions with fewer tests and when you use a tool that integrates the code and the design. A real example of a real application using a real tool makes things seem more, let me say, real.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
|