CI/CD Pipeline Integration

CI/CD (Continuous Integration/Continuous Deployment) automates the process of integrating code changes, running tests, and deploying applications, ensuring faster and more reliable software releases.

CI/CD enables continuous testing and validation, reducing manual effort and minimizing deployment risks. By leveraging tools like Jenkins, GitHub Actions, and GitLab CI/CD, teams can streamline development workflows, detect issues early, and deliver updates seamlessly with minimal downtime.

Step-by-Step Guide

Prefer detailed instructions? Here's a comprehensive step-by-step guide to walk you through the process at your own pace

For Token-related inquiries, please reach out to the ContextQA Administrator.

1. Navigate to your Created Test Plan.

1. Get the Test plan id from the URL.

1. Replace Your ID with the Below curl API.

curl --location 'https://server.contextqa.com/test_plans/{ID}/execution' \
--header 'token: ContextQA Token' \

1. Response to the above URL

{
"id": 1,
"url": "https://demo17.contextqa.com/td/runs/1"
}

1. The above API returns the test result job ID, and the above execution is running in the background, to know the status you need to call the below API.

curl --location 'https://server.contextqa.com/test_plan_results/18/results' \
--header 'token: ContextQA Token' \

1. The result of the above API

{
"result": "FAILURE",
"status": "STATUS_COMPLETED",
"startTime": 1697027039834,
"endTime": 1697027109343,
"duration": 5000,
"totalCount": 1,
"failedCount": 1,
"passedCount": 0,
"abortedCount": 0,
"stoppedCount": 0,
"notExecutedCount": 0
}

"For seamless CI/CD integration, you may refer to the sample YAML file.”