Automate Your API Testing in CI/CD Pipelines
summary
Imports an OpenAPI from SwaggerHub import into Ready API then converts the single XML project into a composite git-friendly layout, builds point-and-click functional tests with chained steps and assertions, and data-drives runs from Excel or Postgres. Virtual services are created and deployed to WorkServer so pipelines hit mocks instead of flaky backends. CI/CD uses the ReadyAPI CLI or TestEngine queueing to start virtual services, fetch a license, run tests in Azure DevOps (or Jenkins/GitHub Actions), publish reports and stop services.
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:48Introducing ReadyAPI
- 6:13Creating a test case
- 8:45Chaining test steps
- 11:02Data sources
- 12:34Data drive
- 13:38Virtual services
- 20:12Git Integration
- 22:48Pipeline Example
- 24:37Test Engine
- 27:30Testing Demo
related talks
16mAPI Platforms, Ready for Testing and Virtualization
13mHelping developers with continuous testing
23mSolving Challenges in API Testing to Achieve More Agile Development
25mRethinking Software Quality: Why API Testing Needs to Change
25mFive Levels of API Automation
54mSolving challenges in API Testing to achieve more agile development
46mAutomated Testing Using Azure DevOps
34mAutotest Coverage Visualization