← Back to Home

Quality Assurance (QA)

1. Definition

Quality Assurance (QA) is a process-oriented approach focused on preventing defects by ensuring that the right processes, standards, and practices are followed throughout the software development lifecycle.

QA answers the question: “Are we following the correct process to build quality software?”

2. Purpose of Quality Assurance

  • Prevent defects rather than detect them
  • Establish quality standards and procedures
  • Ensure consistent development and testing practices
  • Improve overall process efficiency
  • Build confidence in the product and team

3. QA vs Testing (High-Level Understanding)

  • QA focuses on process improvement
  • Testing focuses on product evaluation

QA starts before development and continues throughout the project.

4. What QA Includes (Manual Testing Context)

  • Defining testing standards and guidelines
  • Creating and reviewing QA processes
  • Requirement reviews and walkthroughs
  • Test strategy and planning oversight
  • Process audits and compliance checks
  • Metrics collection and analysis
  • Continuous improvement initiatives

5. QA Activities Across SDLC

SDLC Phase QA Activities
Requirements Requirement reviews, ambiguity identification
Design Design walkthroughs, standards enforcement
Development Process compliance, coding standards checks
Testing Test process audits, coverage review
Release Quality sign-off, risk assessment
Maintenance Root cause analysis, process improvements

6. QA Deliverables

  • QA standards and guidelines
  • Test strategy templates
  • Process documents
  • Quality metrics reports
  • Audit findings
  • Improvement action plans

7. Role of QA in Agile Projects

  • Participate in sprint planning
  • Ensure acceptance criteria quality
  • Promote shift-left testing
  • Encourage collaboration between teams
  • Support continuous feedback loops

8. QA Metrics (Examples)

  • Defect leakage
  • Defect density
  • Requirement coverage
  • Process compliance rate
  • Reopen rate

9. Common Misconceptions About QA

  • QA is not only testing
  • QA does not mean finding bugs
  • QA is not a single person or phase
  • QA is a shared responsibility

10. QA in Real Projects

In real-world projects, QA:

  • Defines how testing should be done
  • Ensures consistency across teams
  • Reduces production issues
  • Improves predictability and delivery quality

11. Interview-Ready Answers

Short answer:

Quality Assurance is a process-focused activity aimed at preventing defects by ensuring the right standards and processes are followed throughout the software development lifecycle.

Detailed answer:

QA ensures that defined processes, standards, and best practices are followed to prevent defects, improve efficiency, and deliver high-quality software consistently.

12. QA vs QC (Preview)

  • QA → Process-oriented, preventive
  • QC → Product-oriented, detective

(QC will be covered as a separate topic.)

13. Key Takeaway

Quality Assurance ensures quality is built into the process, not inspected at the end.