documentation
  • Introduction
    • Overview
      • Scandium Features & Concepts
  • Setting up your account
  • Create a test case
  • Supported Actions
  • File uploads
  • Assertions
  • Groups
  • Step settings
  • Variables
  • System Functions
  • Email Testing
  • Data-driven Testing
  • Test Suites
  • Results
    • Test results
    • Suite results
  • Why did my test fail?
  • API Testing
    • Getting Started
    • API Suites
    • Scheduling and Monitoring
  • Mobile Application Testing
    • Create a mobile project
    • Uploading Apps
      • Android
      • iOS
    • Testing mobile app
  • Common Testing Scenarios
  • Test Management
    • Tests and Folders
    • Tags
  • INTEGRATIONS
    • Continuous Integration (CI/CD)
    • Azure Devops
    • Bamboo CI
    • Bitbucket Pipelines
    • Circle CI
    • Github Actions
  • GitLab CI
  • Jenkins
  • Travis CI
Powered by GitBook
On this page
  • What You’ll Achieve
  • Prerequisites
  • Step 1: Store Secrets in Azure DevOps
  • Step 2: Configure Your YAML Pipeline
  • Step 3: Trigger a Pipeline Run
  • Troubleshooting Tips
  1. INTEGRATIONS

Azure Devops

This guide will help you integrate Scandium into your Azure DevOps pipeline. You’ll be able to trigger and monitor Scandium test executions directly within your Azure build or release pipelines.

PreviousContinuous Integration (CI/CD)NextBamboo CI

Last updated 23 days ago

What You’ll Achieve

By the end of this guide, your Azure DevOps pipeline will:

  • Trigger Scandium test suites.

  • Display live results and logs in the pipeline UI.


Prerequisites

Ensure you have:

  • A account with:

    • Your API_TOKEN

    • A PROJECT_ID and SUITE_ID

  • An Azure DevOps project and pipeline setup

  • Basic understanding of YAML-based pipeline configuration


Step 1: Store Secrets in Azure DevOps

  1. Go to your project settings in Azure DevOps.

  2. Under Pipelines, click on Library.

  3. Create a variable group (e.g., ScandiumVars).

  4. Add the following secrets and check “Keep this value secret” where applicable:

Variable Name

Value / 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

STARTING_URL

(Optional) Starting URL for the tests

BROWSER

(Optional) chrome (default)

SCREENSHOT

(Optional) true or false

VARIABLES

(Optional) '{}' (as JSON string)

RETRY

(Optional) 0

MAX_ATTEMPTS

(Optional) 30

WAIT_PERIOD

(Optional) 120


Step 2: Configure Your YAML Pipeline

Add the following tasks to your pipeline YAML file:

trigger:
  branches:
    include:
      - main

variables:
  - group: ScandiumVars

pool:
  vmImage: 'ubuntu-latest'

steps:
  - script: sudo apt-get update && sudo apt-get install -y jq
    displayName: 'Install jq'

  - script: |
      SCRIPT_URL="https://raw.githubusercontent.com/GetScandium/files/refs/heads/main/scandium_script.sh"
      curl -o scandium_script.sh $SCRIPT_URL
      chmod +x scandium_script.sh
    displayName: 'Download Scandium Script'

  - script: ./scandium_script.sh
    env:
      API_TOKEN: $(API_TOKEN)
      PROJECT_ID: $(PROJECT_ID)
      SUITE_ID: $(SUITE_ID)
      HUB_URL: $(HUB_URL)
      STARTING_URL: $(STARTING_URL)
      BROWSER: $(BROWSER)
      SCREENSHOT: $(SCREENSHOT)
      VARIABLES: $(VARIABLES)
      RETRY: $(RETRY)
      MAX_ATTEMPTS: $(MAX_ATTEMPTS)
      WAIT_PERIOD: $(WAIT_PERIOD)
    displayName: 'Run Scandium Script'

Step 3: Trigger a Pipeline Run

Push code or manually trigger the pipeline from Azure DevOps. You’ll see logs from Scandium directly in your pipeline output.


Troubleshooting Tips

Problem

Solution

❌ Missing environment

Ensure secrets are linked in the variable group and referenced correctly

❌ Script permission

Ensure chmod +x is applied before running the script

🕒 Long wait

Adjust WAIT_PERIOD and MAX_ATTEMPTS



Scandium