Solving Challenges in API Testing to Achieve More Agile Development
summary
Argues for starting testing by middle development and using the OpenAPI contract to run parallel implementation and tests, with automated SDK generation catching regressions (an SDK once broke production). Recommends OpenAPI Generator and API Connect to generate SDKs and test harnesses, and Postman + Newman plus Jenkins for CI runs that exercise real business sequences (e.g., search → reserve → pay). Suggests deploying tests in OpenShift-like near‑prod environments and exploring AI Ops (Watson) to surface patterns and reduce manual triage.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:45Challenges in API Testing
- 3:32Cloud Native
- 6:59Bring Testing in Early
- 13:52Componentization
- 16:19SDK Generation
- 19:15Open API Generator
- 21:00AIOps
related talks
54mSolving challenges in API Testing to achieve more agile development
35mSolving challenges in API Testing to achieve more agile development
25mRethinking Software Quality: Why API Testing Needs to Change
47mNext generation of API testing : Unleashing the power of AI
45mAgile API Development, Bringing Testing and Development Together
54mShould You Be Doing More API Testing?
07m“API Testing in Startups using Postman”
14mAPI First Mindset