CI/CD integrations

Trigger a CloudQA test suite from your build pipeline, wait for it to finish and fail the build when tests fail. Every integration uses the same approach: set a few environment variables, download the CloudQA script and run it.

Jenkins

GitHub

Travis CI

CircleCI

Azure DevOps

AWS CodePipeline

Google Cloud Build

For any other tool, call the web API directly.

What you need

• An API key. Open My Account in CloudQA and copy it.
• A test suite ID. Open the suite’s more-options menu in the Actions column and choose Details. See Test suites.
• jq installed on the build machine, because the script uses it.

Environment variables

Variable	Required	Description
CLOUDQA_API_KEY	Yes	Your CloudQA API key.
CLOUDQA_SUITE_ID	Yes	The ID of the test suite to run.
CLOUDQA_BROWSER	No	The browser to use, Chrome or Firefox.
CLOUDQA_BASE_URL	No	The application’s start URL.
CLOUDQA_BUILD_TAG	No	A build ID or tag, to find the run later.
CLOUDQA_VARIABLES	No	Comma-separated name and value pairs, for example var1=val1,var2=val2.
CLOUDQA_SEQUENTIAL_EXECUTION	No	true runs tests one after another. false allows parallel execution.
CLOUDQA_ENVIRONMENT_NAME	No	The name of the application environment to run against.

Tip

Store your API key as a secret in your CI tool. Don’t write it into a file that is committed to source control or printed in build logs.

The script checks the suite’s status every 10 seconds and shows it in the job log.