Posted by Ben Simo
"I've never read a book about software testing."- too many testers
Quality Frog
Posted by Ben Simo
"I've never read a book about software testing."- too many testers
I am a tester, a skeptic, a defensive pessimist. This blog contains some deep thoughts, some half-baked ideas, and some rambling sentiments. (I'll let you decide which is which.) Whether you agree or disagree with me: you are invited to participate via the blog comments or email.
My opinions may not reflect those of my employer.
Have a question or topic you'd like to see addressed here? Please contact me.
follow me on Twitter1. The value of any practice depends on its context.
2. There are good practices in context, but there are no best practices.
3. People, working together, are the most important part of any project's context.
4. Projects unfold over time in ways that are often not predictable.
5. The product is a solution. If the problem isn't solved, the product doesn't work.
6. Good software testing is a challenging intellectual process.
7. Only through judgment and skill, exercised cooperatively throughout the entire project, are we able to do the right things at the right times to effectively test our products.
4 Comments:
July 10, 2007-
Anonymous wrote:
-
-
July 11, 2007
-
Ben Simo wrote:
-
-
July 12, 2007
-
Anonymous wrote:
-
-
July 13, 2007
-
Jeff Fry wrote:
-
-
Funny you don't have Lee's book on the list - it's actually one of my favorite books on approaches to test design.
Despite it's weight, I'm also a fan of Binders OO testing book - a lot of great stuff on patterns and on approaches for model based testing.
Lee's book is on my bookshelf and I skimmed through it when I got it. I must admit that I haven't yet read much of it. This is primarily because when I skimmed through it, it didn't seem to apply to what I was doing at the time.
I read books that I find interesting. My interest is usually triggered by two things: (1) a current need to solve a problem, and (2) challenges and/or recommendations by people I respect.
Most of the books that I find useful for testing are not testing books. I've got dozens of technical and testing books that I occasionally pull off the shelf for reference or research; but the ones that have influenced me most are not labeled "testing" books.
Now that my interest has been sparked, I'll take another look at Lee's book. And for those that want to see Lee's book, here's a link: A Practitioner's Guide to Software Test Design
Hello Ben,
I must say when I started "official" testing I also didn't read software testing books. And then came a time when I dived in too much into testing books (and not the good ones from todays perspective).
The last books I read were Weinberg's GST and Groopman.
But now I am "boycotting" again and read books which help me to remember my childhood (may be it is because I recently entered the group of people being older than 29 years :-) ).
Greetings from Germany
Hey Ben. Nice list, and it was good to meet you in person at CAST. Here are a few other highlights from my bookshelf:
Weinberg's Quality Software Management series (all I've read so far is v.1, but I've heard good things about each of them.)
Weinberg's Introduction to General Systems Thinking (Not about testing per se, but excellent book about thinking, modeling and problem-solving.)
Dietrich Dorner's The Logic of Failure (social psychological study of how reasonable people's thinking breaks down in complex scenerios. I found this one both fascinating and enormously useful.)
Mike Shema's Hack Notes Web Security Portable Reference (great reference for testing web security.)
Also in my queue is Marick's Everyday Scripting with Ruby, which is designed to help testers (and others) learn to get better at using Ruby or other scripting languages to extend their reach. I haven't read it but am looking forward to it.
Cheers!
Post a Comment