2. Why is QA so important?
How does it look in a *real*
startup-like environment?
3. It looks like:
Constant pressure
Tight schedule
Unending regression
Incomplete test runs
Crossed fingers upon release
4. …and the core goals are:
To provide relevant QA status on a regular basis
To maintain control over the product integrity
To minimize the quality-related risk
To never ship shit
9. Continuous Delivery Pipeline
Repeatable, reliable process for releasing software
Automated building and sanity
Every push is a potential release candidate
and goes through the pipeline
15. Sun Mon Tue Wed Thu Fri Sat
Deploy Branch (4.6.101)
Main Branch (4.6.1)
11:00
Full Merge
Features & Engineering
tasks
Escalations Issues
Build & Deploy
Regression
Escalations Fix for next release
Critical Escalations Fix for
next release
Feature / engineering task for next
release (toggled On)
Feature / engineering task for future
release (toggled Off)
Escalations Fix for future release
Critical regression Fix for
next release
Retest
Build & Deploy
13:00
Push to main &
cherry picking
merge to prod
QA Issues
QA Fix for future release
QA Fix for next release
To QA-Prod,
Staging and Dev
Cluster
To QA-Prod,
Staging and Dev
Cluster
Sun
Deploy to Production
16. Key Points of the flow
Tuesday 13:00 - deployment to staging
Thursday 13:00 - Change Control Board
Go/no go, feature toggle
Sunday 13:00 - deployment to production
QA Cycle: Tuesday - Thursday