Less about tests more about testability - a tester in the platform engineering world
summary
A platform team converts operations into an agile product, defines SLAs/SLOs (99% uptime targets) and enforces blueprint YAML contract files that list maintainers, dependencies, security context and scaling so the platform can automate pipelines. Mandatory health checks, centralized logging and a base image with logging and security enforce testability. A proof-of-concept pipeline reduced environment build time from months to 3 hours to create an environment (still too slow for CI), and a technology-radar plus approval process gates new tools.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:28Automation to platform challenges
- 5:23DevOps teams and platform problems
- 8:42Tester in platform engineering
- 10:50Testers improve platform quality
- 12:35Organizational changes for success
- 14:01Preventing incidents
- 15:46Quality in platform engineering
- 18:13Testability and environment hurdles
- 19:40Testability is essential
- 20:23Safety nets and standardization
- 23:55Agile ceremonies and visibility
- 25:20Blueprint contract
- 26:25Platform blueprint contents
- 31:06Implementing blueprint steps
- 32:10Technology radar and tools
- 37:51Quality lessons from journey
- 40:23Skills for platform teams
- 43:15Building for builders
related talks
27mExploring a DevOps Transformation Like a Tester
15mTransforming Testing: The Power of TestOps
26mThe Impact of Testing on a DevOps Pipeline
13mHelping developers with continuous testing
24mTransformational Change Driven by Transformational Testing.
47mHow Testing is Evolving in DevOps
42mI Don’t Need No Tests
13mFewer Tools, More Impact: An Automated Testing Strategy for Scale-Up