API Testing for Continuous Integration and Deployment
You can use ReadyAPI to run a set of functional API tests as part of your continuous integration via the TestRunner script located in your installation directory. Command-line execution of Ready! API enables you to:
- Control which environment your tests run on (i.e. development, QA, staging, etc...)
- Run either a specific API test case, a whole test suite, or all test suites in a project
- Run a specific subset of tests based on tags at the test case level
- Provide parameters from a previous continuous integration step, such as dynamic host names
Learn more about automating Ready! API for continuous integration in our documentation.
Developers who write their API tests as code (Test Recipes) using the ReadyAPI TestServer SDK can:
- Express API functional tests in Java and other popular languages
- Submit ad-hoc testing tasks to a central testing location
- Build JSON-formatted test recipes that can be shared with other teams
Continuous Integration tools such as Jenkins, Bamboo, and TFS all support post-build triggering of system commands. Much like TestRunner, scripts and compiled test recipes can be sent to TestServer for synchronous or asynchronous execution.
Back To All Features
Learn more about ReadyAPI TestServer here.