Skip to main content

Automating Test Plan Execution with CI/CD on KaneAI

This guide provides a detailed walkthrough for automating the execution of test plans using CI/CD tools such as GitHub Actions or Jenkins on the KaneAI platform. By following these steps, you can effortlessly integrate test plan executions with your pipelines.

Prerequisites

  • Access to Test Manager.
  • A project with KaneAI-generated test cases.
  • Credentials for LambdaTest platform.

Step-by-Step Guide

Step 1: Navigate to the Test Manager

  • Log in to the KaneAI platform and go to the Test Manager page.
  • Access the project where the test plan is located.
Image

Step 2: Locate the 'Test Plans' Section

Inside your selected project, navigate to the Test Plans section. Select the desired test plan for integration or direct triggering from your CI/CD pipeline.

tip

A list of test instances with various configurations will be displayed for each test plan.

Image

Step 3: Copy the Test Plan ID

Open the test plan to view its URL. Copy the Test Plan ID from the URL. This ID will be used in the API call for integration.

Example API Call:

curl --location 'https://test-manager-api.lambdatest.com/api/atm/v1/hyperexecute' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic <Base64Auth>' \
--data '{
"test_plan_id": "YOUR_TEST_PLAN_ID", #enter test plan id
"concurrency": 1, # Optional, Default 1
"title": "UNIQUE_BUILD_NAME", #Optional
"region": "YOUR_DESIRED_REGION" #eastus, centralindia
}'
Image

Example API Response:

{
"jobID": "aea5602b-abcd-1234-abcd-1234abcd1234",
"testBuildID": "01LAMBDATEST2024KANEAIJ8NPGDP",
"jobLink": "https://hyperexecute.lambdatest.com/hyperexecute/task?jobId=<job-id>"
}

Step 4: Configure the API Call

Replace <TestPlanID> with the actual ID from the URL and set additional optional parameters:

  • Concurrency : Defaults to 1 if not specified.
  • Title : Assign a unique job title; a random one will be generated if omitted.
  • Region : Choose a region such as eastus or centralindia.
Image

Step 5: Ensure Job Details Are Unique

Confirm that the job title is unique to avoid conflicts. Select a region if you require a specific allocation for your devices.

Best Practice

Assign clear and descriptive titles to distinguish between jobs.

Image

Step 6: Authenticate and Trigger the Job

  • Provide your LambdaTest username and access key for Basic Authentication.
  • Submit the API call to trigger the job. The process will start within seconds.

Important : Keep your credentials secure to maintain platform integrity.

Image

Step 7: Monitor Test Executions

  • Follow the link provided in the API response to view the HyperExecute Job.
  • Monitor running executions in real time through the dashboard.
Image

Video Explanation

Test across 3000+ combinations of browsers, real devices & OS.

Book Demo

Help and Support

Related Articles