API Testing CI Environment
Last updated
Last updated
This guide describes steps necessary for testing an API described in a swagger file with the in a CI Environment (Jenkins, TeamCity).
The following must be available in the CI environment before testing:
Node.js runtime MUST be available in the CI environment:
MUST be installed globally in the CI environment:
To test an API within the CI environment provisioned as mentioned in the environment prerequisites, you will need the following:
A swagger.yaml
file with the description of API being tested
The OpenAPI Specifciation file should be fetched from . In the case of SwaggerHub API Design Platform, the file can be fetched manually or via their API. Refer to , for details how to use SwaggerHub API.
Alternativelly this can also be a remote file e.g. SwaggerHub URL, if the API is public its OAS file and reachable from the testing host.
The host (address) of the service being tested
Run:
The Dredd will perform the tests and exits usually if the tests have passed. You can check the test result as with any other Unix tools with:
Everything else but 0
should break the build. The test results will be visible in the CLI (log)
See .