Test Automation Requirements Through Recordings
summary
Argues that modern recorders are robust enough to serve as requirements capture, showing examples where a UI recording yields the list of backend APIs so teams skip manual mapping and build API tests quickly. Shows throughput gains: hand-coding a 3-screen, data-driven test takes weeks but a recorded base can be hardened in hours, and API suites run in minutes versus UI suites taking days. Describes workflows where business analysts record base tests and automation engineers reduce script creation from weeks to hours and then harden for CI.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:35HISTORICAL PERSPECTIVE
- 4:08CURRENT INDUSTRY ANALYSIS
- 6:59SOFTWARE DELIVERY CHANGE!
- 9:57CHANGES ALWAYS EVOLVING
- 14:05FIVE KEY RECORDING BENEFITS
- 14:48KEYWORD GENERATION
- 16:40BETTER UI & API STRUCTURE
- 19:11ENGINEERS USE BETTER CODE
- 20:39ALL TESTERS AUTOMATE
- 21:52MAINTAIN BETTER REGRESSIO
- 23:25INDUSTRY FUTURE PREDICTION
- 25:15PERSONAL FUTURE PREDICTIO
- 29:40RECAPPING TODAY'S SESSION
related talks
27mThe Joy of Record and Playback in Test Automation
46mRecord-Replay API Test Cases & Data Mocks without writing code
57mAutomating Test Cases That Aren't Automated
51mRedefining test automation
32mWhy testing is a developer's problem
30mHow AI is Transforming Test Automation
33mRecording Video During Test Runs
50mSOS: I'm a Manual Tester, I Need to Automate and I Don't Know Code