A software testing book from an engineering perspective?

Question

I'm looking for a book that includes methods of testing software from a software engineering perspective.

Specifically, I'm looking for a book that includes black box testing techniques (such as how to test software against different input, etc.), but also includes information about test-driven development/design, unit testing, etc.

What books fulfill these needs?

Answer 1

Code Complete has an extensive and comprehensive chapter on Unit Testing, though my older edition doesn't have TDD and I don't know about the newer one. Pragmatic Unit Testing with C#/Java (C# version) is also a good book, but more focused on unit testing in particular. And, for TDD, there is the authoritative book, Test-Driven Development: By Example.

Answer 2

Keep in mind that black box testing is more for code verification (that have you have good code), not that you're code is right. It's not the only testing you should do.

Answer 3

You might want to check out

"Agile Testing: A Practical Guide for Testers and Agile Teams"

[http://www.amazon.com/Agile-Testing-Practical-Addison-Wesley-Signature/dp/0321534468/ref=sr_1_1?ie=UTF8&s=books&qid=1240892709&sr=8-1][1]

Answer 4

I am loving xUnit Test Patterns by Gerard Meszaros

Answer 5

I've ended up buying Test-Driven Development by Beck, and will buy A Practitioner's Guide to Software Test Design by Lee Copeland. The latter has sort of a recipe approach to software testing, which is exactly what I was looking for. Took a while to find a book like this, too; most software testing books seem to be heavy with reasons why software testing is good, theory, etc.

Answer 6

The granddaddy of engineering-focused software testing books (despite the title) is Glenford Myers' "The Art of Software Testing". Written in 1979, and still just as relevant today !

Answer 7

I think that "A Practitioner's Guide to Software Test Design" by Lee Copeland is too much abstract. Yes, I agree that it contains much fundamental things that are needed in the testing, but it is too much theoretical. I will suggest you "Lessons Learned in Software Testing"