Bitbucket Pipelines
This guide will help you integrate Scandium into your Bitbucket Pipelines workflow. With just a few steps, you’ll be able to run automated tests from your Scandium test suite on every push or PR
What You’ll Achieve
By the end of this guide, your Bitbucket pipeline will:
Automatically run tests from a Scandium suite on every push or PR.
Display test results directly in the Bitbucket Pipelines logs.
Prerequisites
Before you begin, make sure you have:
A Scandium account with:
Your
API_TOKEN
A
PROJECT_ID
andSUITE_ID
A Bitbucket repository with Pipelines enabled
A
bitbucket-pipelines.yml
file in your repository
Step 1: Set Your Bitbucket Repository Variables
Go to your Bitbucket repository.
Click Repository settings > Repository variables (under Pipelines).
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.
Step 2: Create or Update Your bitbucket-pipelines.yml
bitbucket-pipelines.yml
Create or update your bitbucket-pipelines.yml
file with the following:
Step 3: Push to Trigger
Once you’ve committed and pushed your pipeline file, Bitbucket will automatically run the pipeline and execute your Scandium test suite.
Troubleshooting Tips
Problem
Solution
❌ Missing required variable
Double-check that API_TOKEN
, PROJECT_ID
, and SUITE_ID
are set in your repo variables
❌ Script not found or not executable
Ensure the SCRIPT_URL
is valid and script has execution permission (chmod +x
)
🕒 Stuck waiting
Adjust WAIT_PERIOD
and MAX_ATTEMPTS
in the variable section
Last updated