API First Mindset
summary
Argues that shifting testing to APIs cuts fragility and speeds feedback, claiming teams can automate up to 75% via APIs instead of brittle UI suites; gives a concrete pain example where automation waits a 24‑hour feedback delay because it runs only on UI builds. Recommends measuring impact not test count, training testers to build and test APIs, and having leadership require automation at the right layer rather than defaulting to UI.
AI-written summary · about
chapters (9)
- 0:00Introduction to API first mindset
- 1:17Why API layer gets ignored
- 3:49Breaking the UI automation cycle
- 5:37Benefits of API first approach
- 7:02Leadership's role in automation
- 8:49Courage to challenge UI automation
- 11:01Amplifying right voices in automation
- 12:08Recap and mindset shift
- 13:10Final call to action
related talks
54mShould You Be Doing More API Testing?
19mMaster API Automation: Proven Strategies & Tools
26mAPIs & the three pillars of digital transformation
09m"APIs Thinking : Don’t Make it complicated"
25mRethinking Software Quality: Why API Testing Needs to Change
54mAPI's a drivers for innovative business models
23mSolving Challenges in API Testing to Achieve More Agile Development
13mBeyond the hype: What test automation really costs