Rethinking Software Quality: Why API Testing Needs to Change
summary
Claims that API testing must scale to match AI-driven code velocity, showing a concrete workflow: import Swagger or Postman, use AI-generated assertions to build tests, flip a functional test into performance and process tests, and run via GitHub Actions or CI. Platformized demo ties tests to code changes with 34 agents and a SEER framework (sense, evaluate, execute, report) that auto-creates and runs tests and reports failures back into the PR.
AI-written summary · about
chapters (9)
- 0:00Rethinking API quality
- 3:18API testing responsibility
- 7:12AI code volume challenges
- 11:01Nondeterminism in AI APIs
- 15:57AI automation for testing
- 18:47Scaling with agents and validation
- 20:11Q&A Jenkins integration
- 22:03Auto-healing and BDD testing
- 24:10Closing remarks
related talks
23mSolving Challenges in API Testing to Achieve More Agile Development
54mShould You Be Doing More API Testing?
13mFewer Tools, More Impact: An Automated Testing Strategy for Scale-Up
43mAI-Generated API End-to-End Tests: A Legacy Rewrite Case Study
44mHow AI is Exposing the Existential Crisis of Software Testing
47mNext generation of API testing : Unleashing the power of AI
14mAPI First Mindset
36mService Virtualisation and AI for Shift-Left Testing