How to Build a Test Automation Tool That Works in Agile
summary
Tool roadmap shows four levels from Selenium-based code to Gherkin++ codeless scripts to an implementation‑independent model. The actual method is Action State Testing: build abstract steps into a state graph, run two phases. Case data: phase one creates 27 abstract steps and 13 tests; phase two adds 28 steps making 55 steps and 31 tests, with each added test taking <1 minute. Mutation study: exploratory finds 71%, phase one AST 80%, phase two kills 100%. Tool generates Java, targets UI automation.
AI-written summary · about
chapters (21)
- 0:00Test automation in Agile
- 1:49About speaker and Harmony tool
- 2:34Test automation challenges in sprints
- 3:35Gurken++ for test-first approach
- 7:28Adding test design to tool
- 9:18Use case testing independence
- 11:25Limitations of use case testing
- 13:18Selenium maintenance challenges
- 14:44Codeless test automation with Harmony
- 15:26Model-based testing with action state
- 17:55Action state testing cost reduction
- 20:02Coupling effect hypothesis
- 21:49Creating models with action state
- 25:26Validating test steps
- 26:49ATM state transitions example
- 31:11Action state testing advantages
- 33:25Case study metrics and results
- 34:51Mutation testing effectiveness
- 36:17Bug detection with action state
- 38:22Takeaways and cost reduction
- 39:26Q&A on Harmony and action state
related talks
43mCan you Test it
51mRedefining test automation
35mTest Automation by Example
30mTest Automation Maturity Model
14mTest Automation Framework Design and Implementation
18mEffective Test Automation Framework Design
44mThe Test Automation Blueprint: A Case Study
08mEvolving of test automation past to present