Lessons Learned in Software Testing
On July - 30 - 20105 COMMENTS
- ISBN13: 9780471081128
- Condition: New
- Notes: BUY WITH CONFIDENCE, Over one million books sold! 98% Positive feedback. Compare our books, prices and service to the competition. 100% Satisfaction Guaranteed
Product Description
Decades of software testing experience condensed into the most important lessons learned. The world’s leading software testing experts lend you their wisdom and years of experience to help you avoid the most common mistakes in testing software. Each lesson is an assertion related to software testing, followed by an explanation or example that shows you the how, when, and why of the testing lesson. More than just tips, tricks, and pitfalls to avoid, Lesson… More >>
The authors admit the following (on page xxiii):
1- “This is NOT a comprehensive guide to software testing”
2- “This book is NOT a collections of lessons that are always true” (!)
3- “Some lessons that have been usefull and important in our careers may NOT work for you. Use your own judgment” (!!)
4- “This book is NOT a collection of best practices. We don’t believe in best practices” (!!)
This is a real bad book. The only lesson you may have to learn is “how to sell used books in auctions!”
Rating: 1 / 5
This book contains a lot of good information especially for those further removed from the testing process. I’ll let other reviews speak to these issues.
Unfortunately, the authors have polluted their work with politically correct opinions lightly sprinkled throughout the book. The most egregious example is in lesson number 235 on test team diversity.
After correctly pointing out the need for technical diversity and rewarding people based on results, the authors do a 180. Just after stating the dangers of racism, sexism and ageism, they authors engage in racist and sexist discrimination by bashing white males. They state that “…groups…dominated by white males…are particularly counter-productive in testing.” Since testers (are supposed to) analyze things, and I’m a tester, let’s analyze this statement.
If you’re hiring white males just because they are white males and not for their technical ability, then you should expect problems. Ditto for any other race, gender (I’m waiting for this to encompass sexual orientation any day now) or age. In other words, this statement adds no value so why single out and bash white males, except to gain politically correct brownie points. You need to hire on diversity of skill, knowledge and experience, not race, gender or age.
Secondly, the authors imply that all white males think alike. I’m not sure how and where the authors were raised, but from my experience very few white males think alike. So this is defective thinking.
At least 2 of the 3 authors run their own companies. I wonder what their diversity distribution looks like? My guess: They probably have no employees, which may be viewed as “Do as I say, not as I do.”
And for the height of hypocrisy, they should look in the mirror. All three authors are – you guessed it – white males. So while gender and racial diversity is good for your testing group, it’s not necessary for writing a book on testing groups. The authors do not practice what they preach, another defect.
Don’t let these ideological slips prevent you from buying and reading this book. It contains a lot of good information that is sure to surprise those not intimately familiar with software testing.
Notes: For those interested in fighting gender discrimination, see mensactivism.org
If you think that men (of any race) are given societal advantages, read “The Myth of Male Power” by Warren Farrell, Ph.D. You will quickly see that women are routinely given special privileges that men could only dream of having.
Rating: 4 / 5
This book was praised by several colleagues as THE way to work on testing methods and thinking. After reading it and talking with each of them, it was apparent they were excited based on false credentials about ideas that were easy and comfortable but ineffective long term. This book is VERY dangerous to a serious testing organization because it focuses on minimal documentation (which means in 6 months when you’re asked if you tested X and you can’t remember, you’ll get 5mins to get out of the building), downplays automation in regression testing (what!!?), and admits openly that it is proposing ideas that are NOT proven (contrary to what the title states) but rather are ideas that “seem to be working” (see pg 176) but no formal nor long term studies support their claims. Well, long term studies that have already been done directly contradict their findings: process is driven by a need to be effective and if you don’t know what you’re doing before you do it, then you don’t know what you did when you’re done. … This is a book for those who advocate ad hoc testing to their own discredit and need a means of justificating their apathy and laziness to those who actually know effective testing techniques.
Rating: 1 / 5
A great book if you have some experience in software testing and would like more real life hints and tips.
Rating: 5 / 5
Hi All,
This is one of the best book which i have gone through for the testing lessons learned. The author done really good research about the current software testing problems. Worth buying..
I am very happy ..
Thanks
Guru
Rating: 5 / 5