- Series: Addison-Wesley Signature Series (Cohn)
- Paperback: 352 pages
- Publisher: Addison-Wesley Professional; 1 edition (September 16, 2016)
- Language: English
- ISBN-10: 0134291069
- ISBN-13: 978-0134291062
- Product Dimensions: 7 x 1 x 9 inches
- Shipping Weight: 1 pounds (View shipping rates and policies)
- Average Customer Review: 7 customer reviews
- Amazon Best Sellers Rank: #1,023,073 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Developer Testing: Building Quality into Software (Addison-Wesley Signature Series (Cohn)) 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Frequently bought together
Customers who bought this item also bought
About the Author
Alexander Tarlinder wrote his first computer program around the age of ten, sometime in the early nineties. It was a simple, text-based role playing game for the Commodore 64. It had lots of GOTO statements and an abundance of duplicated code. Still, to him, this was the most fantastic piece of software ever conceived, and an entry point to his future career.
Twenty-five years later, Alexander still writes code and remains a developer at heart. Today, his professional career stretches over 15 years, a time during which he has shouldered a variety of roles: developer, architect, project manager, ScrumMaster, tester, and agile coach. In all these roles, he has gravitated towards sustainable pace, craftsmanship, and attention to quality, and he eventually got test infected around 2005. In a way, this was inevitable, since many of his projects involved programming money somehow (in the banking and gaming industry), and he always felt that he could do more to ensure the quality of his code before handing it over to someone else.
Presently, Alexander seeks roles that allow him to influence the implementation process on a larger scale. He combines development projects with training and coaching, and he shares technical and nontechnical aspects of developer testing and quality assurance in conferences and local user groups meetings.
Try the Kindle edition and experience these great reading features:
Showing 1-7 of 7 reviews
There was a problem filtering reviews right now. Please try again later.
Consequently, I would highly recommend to my top management to purchase several hard copies of this book and make them available in our physical library as I am convinced this title will become indispensible within our Software Development Centre!
The sub-title really gets at the heart of what the book is about: __Building Quality Into Software__
I also like this book a lot because it keeps the subject fresh and interesting all the while providing me with additional ideas and new angles to view my software development from.
This book is about far more than just Unit Testing or testing software, it is really about the right way to run a software project and how to consider testing as a part of the entire System Development Life Cycle as it should be.
This is an important book in the published body of software architecture and software development and will keep your interest and make you a better developer as a part of a team creating software with fewer defects that is easier to maintain and extend.
Alexander Tarlinder starts from the beginning, by defining what developer testing is and by explaining common testing terms. Then he writes about what you can do, as you design and write your program, to make it testable. This includes observability and controllability. In my view, this is the best part of the book.
Next he describes different ways and styles of writing automatic tests. Topics covered include unit test naming, TDD examples (both classic and mockist style), test doubles and mocking frameworks. The chapters are clear and easy to read, and the summaries at the end of each chapter are some of the best I have read in any technical book.
The topic of developer testing is important, and all developers should know the basics presented in this book.
All concepts and practices applied to the test subject are very well explained with references and the most important for developers: code!
If you are a developer you'll understand a lot of concepts and practices to expand you knowledge and create software with quality.
If you are a tester you'll the "dark side" and understand there is no side. You'll gain knowledge in development and see that many things to apply is not so ease as we think.