Should You Be Doing More API Testing?
summary
Argues that shifting most regression work from flaky UI scripts to API tests cuts maintenance and speeds "in‑sprint" automation, shows a concrete toolchain using Karate (HTTP tests, built‑in API mocking, HTML failure diagnostics) plus Gatling for load reuse, cites 7,000 stars on GitHub as adoption evidence, and demonstrates tests running and producing readable reports. Claims API tests need less coding than Selenium/Cypress, run parallel easily, and can be reused directly as performance tests (reuse as performance tests).
AI-written summary · about
chapters (8)
- 0:00Why API testing matters
- 7:27APIs in modern systems
- 10:07UI vs API testing trade-offs
- 20:46Advantages of API testing
- 32:05When to use API vs UI tests
- 33:09Introducing Karate framework
- 39:12Live Karate demo
- 45:24Q&A session
related talks
19mMaster API Automation: Proven Strategies & Tools
14mAPI First Mindset
25mRethinking Software Quality: Why API Testing Needs to Change
44mKarate: Beyond API testing
16mAPI and UI Test Automation with Karate
13mFewer Tools, More Impact: An Automated Testing Strategy for Scale-Up
23mSolving Challenges in API Testing to Achieve More Agile Development
21mThe Essential Pillars of Automation Testing for Success