Pipelines and quality gates

18 min · Module 22

CI runs on every change; CD deploys continuously or on demand. Quality gates fail the pipeline when critical checks fail (lint, unit, API, UI smoke, security scan).

Lab analogy: don’t “deploy” 1.1.0-rc to stakeholders without failing QA-103 if search is broken—your gate is the work board sign-off.

Example / notes

# Example gate order
# lint → unit → API contract → UI smoke → (optional) perf budget → deploy

Practice in Lab: /lab/releases/

Environments and progressive delivery →

Modules in this track

15. QA Foundations — Strategy & Planning
- Writing a test strategy
- Test planning and estimation
16. Test Design Techniques
17. API & Contract Testing
- HTTP API testing fundamentals
- Contract and schema testing
18. Performance Testing Basics
- Performance concepts and SLOs
- Designing a minimal performance check
19. Security Testing Basics
- Auth, sessions, and authorization
- OWASP-minded checks for web apps
20. Accessibility Testing
- Accessible by design checks
- Automated a11y smoke
21. Mobile Testing
- Mobile web quality risks
- Native apps and device farms (overview)
22. CI/CD, Quality Gates & Environments
- Pipelines and quality gates
- Environments and progressive delivery
23. Test Data, Environments & Observability
- Test data management
- Observability for QA
24. Soft Skills — Stakeholders, Mentoring, Metrics
- Stakeholder communication
- Mentoring and quality metrics/OKRs
25. Career & Process — Agile, Compliance, Senior Bar