Overview
Verifying the Final Output
QC is the 'Check' phase of the Plan-Do-Check-Act cycle. It ensures that despite the best processes, the specific software build is ready for the user.
QC involves technical verification. This includes executing test cases, running automated suites, performing regression testing, and conducting security scans to find and report defects.
Our Recommendation
9/ 10
Best Practices
Dos and Don'ts
Avoid common mistakes that can lead to flaky tests and maintenance nightmares.
What to do
- •Use objective pass/fail criteria for all QC activities.
- •Automate repetitive QC tasks to allow for manual exploratory testing.
- •Ensure the test environment is an exact mirror of production for accurate QC.
Common Pitfalls
- •Don't rely solely on QC; if you are finding 50 bugs a day in QC, your QA process is broken.
- •Don't pass a build that fails critical QC checks just to meet a deadline.
The Details
QC in the Modern CI/CD Pipeline
In modern DevOps, QC is continuous. Every time a developer commits code, automated QC checks (Unit, Linting, Integration) run instantly. This 'Continuous Quality Control' provides immediate feedback, allowing for much faster delivery cycles than traditional 'Waterfall' QC phases.