Effective Software Testing: A Developer's Guide

Solid book on developer testing. I particularly like chapters 2 and 3 - a systematic way of coming up with test cases, based on both the specification and the structure of the code. Also, the examples are great throughout the book - not too simplistic, but still small enough to keep in your head.The author is a professor of Software Engineering, but has also worked as a developer. This shows in the book: it is quite pedagogical, with many interesting and relevant references to research. There are also many instances where he uses his own experience in the discussions of different techniques.I have written a much longer review on my blog (can be found by searching).

This is a fantastic book for learning software testing techniques. The book does a great job of showing how to move from testing as an ad hoc and unstructured haphazard activity to structured activity. The book is a great mix of principles around how much testing is enough, what guarantees we can get from testing, but also illustrates specific techniques that can help developers, such as test doubles, how to effectively use code coverage, and more. Another chapter that I really enjoyed was the chapter on test code quality. Often beginning programmers can easily understand the difference between having tests and not having tests, but the difference between good tests and bad tests can be much more subtle, and a lot harder to grasp. There are lots of code examples sprinkled throughout the book as well.I would strongly recommend this book to anyone who wants to get better at testing.disclaimer: I was provide a review copy of this book from the publisher, but I have since purchased more copies on my own.

Livro excelente, explica o conteúdo de forma objetiva e com exemplos claros.

This book gives a to-the-point introduction to basic software testing techniques. The biggest part focusses on unit testing including things such as code coverage, deciding what to test on unit-test level and mocking of dependencies. This gets complemented by one chapter on larger tests such as system and integration tests and one chapter presenting some best-practices and anit-patterns. All examples are written in Java, but even without a Java-background easy to understand.I was tempted to rate it with 4 instead of 5 stars, because as someone with interest in the topic, but without thorough experience (i.e. i have read some blog articles and written a couple of tests, but never mindfully designed test suites for our systems) there was not a lot of new information inside. Then I however decided to go with 5 starts nevertheless, because as an introductory book it really gives a great overview on the topic.