Slide 22
Slide 22 text
Test Automation
Traditional Automation Pipeline Driven Automation
collaborative
model
RD: UT &| AE: IT & E2E Discuss “Acceptance Criteria” TOGETHER
KPI Automation coverage rate KEY examples (scenario) coverage
Pipeline # Multiple pipelines One pipeline to production
De
fi
nitive Verdict Blue / Yellow / Red, human verdict Success / Fail
Automation
Strategy
What ever works in a 2-week cycle Modularized, stub, test isolation, testContext, …
Traits Alpha, beta, staging, production CUJ coverage, Release strategies, O11y
Branching
Strategy
Feature Branches Trunk-based development + feature toggle
Continuous
Improvement
Get “Green” before scheduled release Continuously improve pipeline cycle-time