Jenkins
This guide will help you integrate Scandium into your Jenkins pipeline. With just a few steps, you’ll be able to run automated tests from your Scandium test suite as part of your CI/CD process.
Last updated
This guide will help you integrate Scandium into your Jenkins pipeline. With just a few steps, you’ll be able to run automated tests from your Scandium test suite as part of your CI/CD process.
Last updated
By the end of this guide, your Jenkins job will:
Automatically run tests from a Scandium suite during the build process.
Display test results directly in Jenkins console output.
Before you begin, make sure you have:
A account with:
Your API_TOKEN
A PROJECT_ID
and SUITE_ID
Jenkins installed and running
curl
and jq
installed on the Jenkins build agent
A Freestyle project or Pipeline job configured in Jenkins
You can set environment variables in two ways:
Navigate to Manage Jenkins > Configure System.
Under Global properties, check Environment variables.
Add the following variables:
Variable Name
Description
API_TOKEN
Your Scandium API token
PROJECT_ID
Your Scandium project ID
SUITE_ID
Your Scandium test suite ID
HUB_URL
(Optional) Selenium Grid URL, if running on your infrastructure
STARTING_URL
(Optional) The URL your tests should start from. This will override all tests within the suite you are executing.
Jenkinsfile
should look like this:Trigger your Jenkins job manually or on a git push event. Your Scandium test suite will execute as part of the build process.
Problem
Solution
❌ Missing required variable
Ensure API_TOKEN
, PROJECT_ID
, and SUITE_ID
are set in Jenkins env vars
❌ Script not found or not executable
Double-check the script URL and ensure it has execution permissions (chmod +x
)
🕒 Stuck waiting
Adjust WAIT_PERIOD
and MAX_ATTEMPTS
in the Jenkinsfile