„Complete” In-Sprint Testing Using Collaborative Models
summary
Claims four barriers block scaling automation and shows model‑based, collaborative modeling that generates optimized tests as systems change; numbers include 15–20% automated 80% manual and examples like 10,000 functional tests producing combinatorial billions and a generated set of 146 parts reduced to 7; concrete tooling and pipeline: Cypress + Azure DevOps + CircleCI and Modello converts JSON schemas into REST calls, producing end‑to‑end tests in minutes and demonstrated working at scale.
AI-written summary · about
chapters (12)
- 0:00In-sprint testing challenges
- 3:49Why test automation fails
- 5:14Model-based testing benefits
- 8:28Live demo workflow
- 11:56Advanced architecture example
- 14:42Adoption roadmap
- 17:54Quick adoption tips
- 18:39Q&A: Maintaining tests
- 19:23Q&A: Test levels for products
- 20:27Q&A: Test case accuracy
- 21:10Q&A: Time to implement
- 22:14Q&A: Handling test data
related talks
58mTesting Strategy - New Model, Better Outcomes
18mEffective Test Automation Framework Design
10mModel Based Test Automation
32mWhy testing is a developer's problem
35mScalable Testing Strategies
01h 08mTest Automation Monsters
30mBest Practices for Accelerating Continuous Testing
57mOptimizing Your Testing Team