Put your TestOps shoes on
summary
Provides three concrete automations: pick the minimal regression suite via an API to run only relevant tests, drive Jira workflow transitions after deployment, and ingest Crashlytics metrics to create alerts and auto-create tickets. Uses specific tools — Zephyr, Jira, Slack, Jenkins — and reports measurable wins (examples claim ~30–50% faster test cycles and catching regressions before angry users). Emphasis is on quick wins and runnable recipes rather than high‑level theory.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 2:50Traditional software testing
- 5:00What is TestOps
- 9:00Process perspective
- 11:20What is test ops
- 12:10Why we should care
- 12:40Two types of tests
- 13:30Flaky tests
- 14:35Continuous delivery
- 18:05Unicorn Dilemma
- 18:35Speed vs Quality
- 19:50Tools vs Process
- 20:25Adhoc testing
- 20:50Test cases
- 21:15Test suites
- 22:40Quality test cases
- 24:20Jenkins Rocket Science
- 25:30Kanban
- 29:55Crashlytics
- 32:10Process
- 33:20Creating bugs
- 33:55One problem
- 36:10Developers role
- 37:20Summary
- 41:40Outro
related talks
36mPut Your TestOps Shoes on! Improving Quality by Process Automation
15mTransforming Testing: The Power of TestOps
40mDo You Care about Requirements Management and Traceability? Use TestOps and Atlassian
46mA Practical Guide to Testing in DevOps
56mTestOps at scale
25mDevOps Handbook Experiments in Accelerating Delivery
21mThe Essential Pillars of Automation Testing for Success
27mExploring a DevOps Transformation Like a Tester