Solving challenges in API Testing to achieve more agile development
summary
Claims a team can auto-generate tests from an endpoint (no full OpenAPI spec required), produce contract tests that fail when payload fields or types change, and integrate those tests into CI/CD so regressions run on every build. Recommends the API provider or product owner own test suites, version contract tests alongside API versions, and push selected checks into production monitoring (example: run key contract tests every 15 minutes). IBM tooling is positioned as the automation enabler.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 7:56API testing in agile
- 10:00API testing challenges
- 21:33Validating API contracts
- 24:41API testing without docs
- 28:10Early API test automation
- 32:22API versioning in testing
- 36:13API test case ownership
- 40:04API quality metrics
- 43:32Hidden API test cases
- 49:13Key takeaways
related talks
35mSolving challenges in API Testing to achieve more agile development
23mSolving Challenges in API Testing to Achieve More Agile Development
13mHelping developers with continuous testing
25mRethinking Software Quality: Why API Testing Needs to Change
54mShould You Be Doing More API Testing?
47mNext generation of API testing : Unleashing the power of AI
13mFewer Tools, More Impact: An Automated Testing Strategy for Scale-Up
19mMaster API Automation: Proven Strategies & Tools