What are your Automation Strategies?
summary
Claim: responsibility for automation is everyone in the delivery team, not just QA. Practical choices: pick codeless vs script-based based on team skill and buy a tool that fits your ecosystem (examples heard: Cypress, Docker, Jenkins, cloud providers). Build a small proof-of-concept first, measure ROI with baseline metrics (tests per requirement, % automated, complexity, number of configs) and expect gains in deployment speed and team happiness.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:00Agenda
- 1:35About Lisette
- 2:34Lets get started
- 3:20Why are we here
- 4:28Who are we
- 7:20Who is responsible for automation
- 10:59Typical pain points
- 13:12What is your pain point
- 14:18The result of your pain point
- 15:08Current trend
- 16:24Tools
- 17:17Tradeoff
- 19:02Define your why
- 20:36Framework Tool
- 23:45AIbased Tool
- 25:08Activity Time
- 30:38Solution
- 36:55Team Activity
- 38:07Take Away
- 39:17Next Step
- 41:33Teamwork
- 42:18Recap
- 42:56QA
related talks
38mAutomation Is Hard & We Are Doing It Wrong
08mReviewing your test automation strategy"
21mMindful Automation Testing Software Builds and Streamlining Processes
19mBusiness Impact Delivery Using Test Automation
13mThe Automation Firehose Be Strategic and Tactical
48mAutomate and You Shall Conquer
13mFewer Tools, More Impact: An Automated Testing Strategy for Scale-Up
04mAutomate!