Is quality assurance the same as testing and bug fixing?

Question

What is a quality guarantee? Is it testing and bug fixing, or is it something more?

Answer 1

QA software includes the entire software development process — monitoring and improving the process, ensuring that agreed standards and procedures are followed, and that problems are identified and resolved.

details: Frequently Asked Questions on Software Quality Assurance

Answer 2

Q) What is quality assurance?

• Quality Assurance refers to processes and procedures that systematically monitor various aspects of a service , process, or tool to detect, correct, and enforce quality standards.

• Quality assurance has helped us eliminate defective products and increase customer satisfaction.

Q) Is it testing and bug fixing, or is it something more?

• Quality assurance is more than testing. It provides a framework for determining how quality is defined in the organization, and it should be implemented in the organization. The processes and procedures related to quality will be defined here.

• applies to the entire software development process , carefully studies and monitors the software development process, corrects the process problems that they find, performs testing and has the power to decide when the product is ready for release.

• The main goal is "no errors," rather than keeping the product on schedule or budget.

so the above point clarifies that this QA is much more than testing :)

Answer 3

QA is much more than bug fixing and testing. It is also more than checking a product for a certain amount (although this is an important part).

QA should occur at all stages of the project or phase of the project. Requirements must comply with QA to guarantee their relevance, reachability and so on. Unit tests must have QA to ensure adequate application coverage. Please note that this is not a test that the test is working, but the tests are generally “good enough”. The code itself must undergo QA in the form of code reviews and unit tests.

These QA activities do not have to be performed by a separate department. Code reviews are what should and should be done by other developers.

If (and this is large, if), there is a sufficient amount of QA in the entire project, then the amount of error checking / correction that occurs at the end of the project phase should be minimized.

Answer 4

QA = Testing, validation and verification.

Bug fix is ​​not a tester. while the tester may indicate errors for the programmer.

Testing is also part of one of the five stages of software development.

Usually at the last stage (maintenance / amplification) material is used to correct errors.

But throughout the entire development life cycle of SW, errors are detected through testing either by client or by programmer.

Answer 5

QA is a short form of quality assurance.

Quality Assurance means checking a product for a specific area in which a scope is performed or not. It includes testing bug fixes and other things.

The first QA team will check the product for a specific area, and if they find an error or improper functionality of the product, they will send an error message and be assigned to the developer who developed this product.

The developer will fix these problems with an error. The QA team will check the same again and check this.

This cycle will continue until a certain project volume is satisfied.

You can also find additional information at the following links.

QA definition:

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

Error correction definition

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

Testing Definition

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 results and definitions on google

Greetings

Answer 6

Quality assurance starts right from the initial stage of any project. It includes the implementation of many processes and procedures established by the organization to achieve certain goals in the field of quality.

Validation is an important part of quality assurance. You must confirm the availability of the required result or requirements.

There is no error-free software in the world on any platform that the user uses. The goal is to get an intelligent product with the maximum number of cases sorted and processed in software. By use and case, I mean the maximum number of client behavioral cases

You can assure the quality of your product only when you have a set of documentary evidence. Evidence that you completed the entire process and all tasks were completed.

The QA team has many responsibilities when it comes to certification of organization standardization. e.g. certificates like ISO 9001: 2008

Answer 7

For real-world definitions (yes, not just one) of quality assurance, you can check ISO 24765, which is the standard that defines software conditions. (I don't think I'm allowed to copy paste definitions here, so I'm just making a link). ISO 24765 regroups the definitions of ISO 12207 and ISO 15288 so that you can also check out two points. CMMI also provides its own definition of QA.

For information:

ISO 12207 -> Systems and software engineering - Software life cycle processes. ISO 15288 -> Systems and software engineering - System life cycle processes. ISO 24765 -> Systems and software engineering - Vocabulary 

I would define quality assurance in 2 parts.

=> (software) Quality assurance is a systematic way of gaining confidence that software will be consistent with quality. QA consists of processes → Activities → Tasks → Procedures. The number of processes and the depth in which processes will be laid out in “Actions, Tasks and Procedures” usually depends on the size of the team and the criticality of the software being developed. QA will mainly try to prevent defects, while Quality Control will try to identify defects (therefore, I believe that error correction is not part of QA, but is part of quality control). QA has testing processes, but it is more focused on integration and qualification testing.

=> Quality is the degree to which the software will satisfy the needs of the client (both said and never said), requirements and expectations. (Please note that it is rather difficult to find out about the unexplained needs of the client and the expectations of the client).

Answer 8

Testing and bug fixing and validation are part of the QA. But QA as such is a process / practice to ensure the promised quality. Thus, QA can include ensuring that the requirements are complete / Requirements are valid / The correct build process is implemented / Dev practices good coding techniques. Not everything is implemented in all projects, but it is part of QA