CI/CD integration using REST API

Trigger test suite details and get build status using CI CD REST API

You can now integrate with your existing CI tools with Low Code Automation to achieve the following objectives:

• Automatically trigger low code tests upon deployment to the staging environment
• Trigger critical tests on each commit to a pull request, or based on specific conditions
• Incorporate low code tests into your existing sanity/regression pipeline jobs

API’s to trigger Test suite and get build status

Use REST API to trigger test suite’s and to get the build status.

Prerequisites

• BrowserStack Username and Access key. You can find this in your account profile section. If you do not have an account yet, sign up for a Free Trial.
• Test suite ID. You can find this on your test suite details page.
  

REST API details

Use the curl commands to trigger test suites and get build statuses. In the curl requests, replace the YOUR_USERNAME and YOUR_ACCESS_KEY variables with your account’s username and access-key.

Trigger test suite
Use the following curl command to trigger Low Code Automation test suites based on the TEST_SUITE_ID specified:

Replace TEST_SUITE_ID with the id of the test suite you want to trigger.
The response returns a JSON object, which contains the build_id that you can use to fetch the test suite execution status.

Fetch build status

Use the following curl command to fetch the status of build execution for the BUILD_ID specified:

Replace BUILD_ID with the build_id value you receive from the Trigger test suite API.

Integration with CI/CD pipelines

You can integrate with any of your existing CI/CD pipelines. Following are a some of the examples of popular CI tools which can be integrated using the REST APIs mentioned above

• Jenkins
• Azure Pipelines
• Bitbucket Pipelines
• Circle CI
• Travis CI
• Gitlab CI/CD
• Github Actions