Does Quality Assurance = Testing & Bug Fixing?

Question

What is Quality Assurance? Is it testing and bug fixing, or is it something more?

Answer 1

QA = Testing, it validate and verify.

Bug fix is not the job of tester. while tester can indicate bugs for programmer.

Testing is also among one of the five stage in software development.

Usually, last stage(maintenance/enhancement) is involved with bug fixation stuff.

But during the whole life cycle of SW development, bugs are identified through testing, or by customer, or by programmer.

Answer 2

Software QA involves the entire software development process - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with.

more detail: Software QA FAQ

Answer 3

QA is the short form of Quality Assurance.

Quality Assurance means Checking a product against the defined scope where the scope is fulfilled or not. It includes the testing bug fixing and other things.

First QA Team will check the product against the defined scope and If they found mistake or improper functionality in product then they will post a bug and assigned to a developer who had developed this product.

Developer will fix this issues called bug. QA Team will again check the same thing and verified this.

This cycle will continue until and unless the defined scope of project is satisfied.

You can also find further information from the following links..

Definition Of QA:

http://www.google.co.in/search?hl=en&defl=en&q=define:Quality+assurance&ei=vzUDSvqLCKjq6gP2v6yaAw&sa=X&oi=glossary_definition&ct=title

Definition OF Bug Fixing

http://encyclopedia2.thefreedictionary.com/bug+fix

Definition Of Testing

http://searchwindevelopment.techtarget.com/sDefinition/0,,sid8_gci534970,00.html

Other links:

http://www.softwaretestinghelp.com/types-of-software-testing/ http://www.exforsys.com/tutorials/testing/bug-life-cycle-guidelines.html http://www.onlamp.com/pub/a/onlamp/2005/08/11/fixingbugs.html

Hope this helps you

You can still find millions of result and definition in google

Cheers,

Answer 4

QA is much more than bug fixing and testing. It's also more than checking the product against the defined scope (though that is an important part).

QA should be happening at all stages of the project or project phase. The requirements should be subject to QA to ensure that they are meaningful, achievable and so on. The unit tests should be subject to QA to ensure that they give sufficient coverage to the application. Note this isn't checking that the test works but that the tests as whole are "good enough". The code itself should be subject to QA in the form of code reviews and unit tests.

These QA activities don't have to be carried out by a separate department - code reviews are something that are and should be done by fellow developers.

If (and it's a big if) there is sufficient QA throughout the project then the amount of testing/bug fixing that happens at the end of a project phase should be kept to a minimum.