Unit
- Quality assurance vs. quality control: QA is a proactive, process-oriented discipline focused on preventing defects by improving development and testing processes. Quality control is a reactive, product-oriented activity that identifies defects after the product is built. The distinction is critical for designing an effective testing strategy.
- QA as a stakeholder function: QA professionals collaborate with developers, product managers, business analysts, and operations teams. They provide a quality perspective throughout the software development lifecycle, from requirements gathering to post-release monitoring. This cross-functional role demands strong communication and analytical skills.
- Cost of quality: The earlier a defect is detected, the lower the cost to fix it. Industry studies show that fixing a defect during requirements costs a fraction of fixing it in production. QA activities like reviews and static testing reduce downstream costs and protect brand reputation.
- QA in different development methodologies: In Waterfall, QA is a distinct phase after coding. In Agile, testing is continuous and integrated into each sprint. DevOps requires automated testing in the deployment pipeline. Understanding these variations helps QA professionals adapt their approach.
- Shift-left testing: This practice moves testing activities earlier in the lifecycle, such as reviewing requirements and designing tests before code is written. It reduces rework and accelerates delivery. Techniques include static analysis, acceptance test-driven development, and behavior-driven development.
- Shift-right testing: Testing continues after release through production monitoring, canary releases, A/B testing, and user feedback analysis. It validates real-world behavior and catches issues that emerge under live conditions. This complements shift-left efforts.
- Quality culture: Organizations with a strong quality culture encourage everyone to take ownership of quality, not just the QA team. This includes peer code reviews, continuous learning, and celebrating quality achievements. Leadership commitment is essential to sustain such a culture.
- Common QA pitfalls: Relying solely on manual testing, missing test documentation, ignoring non-functional requirements, and treating QA as a gate at the end of development. Awareness of these pitfalls helps professionals avoid them and advocate for better practices.
- Test planning and estimation: A test plan outlines scope, resources, schedule, and risks for a testing effort. Estimation techniques such as function point analysis, work breakdown structures, and historical data help QA teams allocate time accurately and set realistic milestones.
- Test case design techniques: Equivalence partitioning, boundary value analysis, decision tables, and state transition testing are structured methods for selecting test cases. These techniques increase coverage and efficiency, ensuring that both valid and invalid inputs are examined systematically.
- Defect tracking and lifecycle: Defects are logged, triaged, assigned, fixed, verified, and closed through a formal process. A defect tracking system records severity, priority, environment details, and reproduction steps. Effective tracking provides metrics for process improvement and product quality assessment.
Strategic Framework
Framework: V-Model (Verification and Validation Model)
Purpose: Maps each development phase to a corresponding testing phase, emphasizing early verification and late validation.
- Requirements analysis: Corresponds to acceptance testing. Ensures the product meets user needs.
- System design: Corresponds to system testing. Validates overall system behavior.
- Architecture design: Corresponds to integration testing. Checks component interactions.
- Module design: Corresponds to unit testing. Verifies individual functions.
Quick Revision
- QA is proactive; QC is reactive.
- QA collaborates across the lifecycle to prevent defects.
- Cost of fixing defects increases exponentially over time.
- Shift-left and shift-right testing cover pre- and post-release quality.
- V-Model pairs each development phase with a test phase.