Testing is NOT Quality Assurance (QA)

I decided to write this short entry because I think it’s a common confusion.

The main goal of software testing is to find bugs as soon as possible and make sure they get fixed. (Patton)

The main goal of software quality assurance (SQA) is to provide methodologies and standards to monitor and improve the development process, preventing the maximum possible bugs and delivering high quality products. (Patton)

But it doesn’t mean SQA profissionals don’t do tests and software testers don’t help with some SQA tasks. There are some overlaps, but the main responsabilities of each one is very clear. In fact, the SQA team uses the testing team as part of the methods to help increase quality.

The software testing team doesn’t have means to assure that the software will be of high quality. Their job is to find bugs as soon as possible and make sure they get fixed, but if developers don’t fix them, it’s not their fault. But it is the SQA team, who is responsible to deliver high quality products, which includes maintaining a qualified development team.

The internal structure of a company will define how relationships and responsabilities are distributed between teams, which may include executive management, project management, SQA, testing, development, etc.

What is Software Testing?
What really is a software bug?
What is a Product Specification?
How to Report Bugs Effectively

Software testing (Wikipedia)
Software Testing Help
Software testability (Wikipedia)


Patton, Ron. Software Testing. 2nd ed. Sams, 2005.

comments powered by Disqus