intermediate · cohort · 5 weeks · 7–9 hrs/week
CI Pipelines for Testers
Read YAML, stage tests intelligently, and communicate pipeline failures without blaming runners.
¥72,000 JPY — informational list price
Overview
You fork sample pipelines, add caching thoughtfully, and learn when reruns hide product risk. Labs use GitHub Actions with parallels to other providers documented in appendix notes.
What is included
- Cache vs artifact decisions spelled out
- Matrix strategies that do not explode minutes
- Secrets handling overview for testers collaborating with DevOps
- Failure annotations that show up in PR checks
- Flake detection signals worth alerting on
- Blue/green mentions without vendor lock-in
- Cost dashboards testers can actually read
Outcomes you can evidence
- Propose pipeline changes with measured impact
- Identify redundant jobs burning minutes
- Pair with developers using shared vocabulary
Lead mentor
Lina Park
Career coach bridging QA goals with platform engineering constraints.
Avatars load from ui-avatars.com with a styled fallback if blocked.
FAQ
Examples use GitHub-hosted runners; mapping notes for GitLab and others included.
Experience notes
“CI Pipelines for Testers gave me language to challenge “just rerun” culture with data from our minute usage chart.”