Azure DevOps (ado)

Azure DevOps test repository adapter for ABAP Agent 2.0 — CLI and Guides references.

Use adapter type ado to connect an Azure DevOps organization/project so the agent can search test cases for your pipeline.

When you create the ABAP pipeline with pipeline set, leave --labid unset unless you deliberately need to override it. The agent derives the default lab ID as <QAS SID> <QAS RFC hostname>. Casual overrides can break Test Cycles in SeaLights. See Create and list pipelines.

Configure

• Configure Test Repositories — slabapcli testrepo set --type ado
• Setup and installation (Part 1)
• Show the value with Test Cycles (Part 2)

testrepo set parameters for ado

Non-secret keys use --setting key=value. Secrets are entered interactively (not via --setting). Plus common options (--name, --type, --pipeline, --test-stage) — see Configure Test Repositories.

ado does not accept confidenceThreshold.

Parameter	Kind	Required	Description
url	Setting	Yes	The Azure DevOps organization or collection URL (for example https://dev.azure.com/MyOrg).
project	Setting	Yes	The Azure DevOps project name.
timeout	Setting	No	Integer (seconds). Per-repository request timeout.
searchPaths	Setting	No	Comma-separated list that scopes the search to specific paths. Written as top-level searchpaths in config.toml.
password	Secret	Yes	Azure DevOps Personal Access Token (PAT).

Command Prompt

Command

slabapcli.exe testrepo set --name "ALM_Demo-ado" --type "ado" --pipeline "ALM_Demo-S21" --setting url=https://dev.azure.com/MyOrg --setting project=MyProject --test-stage "Regression Tests"

PowerShell

Command

.\slabapcli.exe testrepo set --name 'ALM_Demo-ado' --type 'ado' --pipeline 'ALM_Demo-S21' --setting url=https://dev.azure.com/MyOrg --setting project=MyProject --test-stage 'Regression Tests'

--test-stage is optional. See Configure Test Repositories for the default "{type} Tests" value, clear-on-omit behavior, and duplicate-stage warning.

The CLI prompts for a Personal Access Token as password interactively (secrets are not accepted via --setting).

Expected output (PowerShell, abbreviated)

.\slabapcli.exe testrepo set --name 'ALM_Demo-ado' --type 'ado' --pipeline 'ALM_Demo-S21' --setting url=https://dev.azure.com/MyOrg --setting project=MyProject --test-stage 'Regression Tests'
[2026-03-08 10:45:00.123+02:00] [info] Config pathname: C:\ProgramData\Tricentis\SeaLights\ABAP Agent\config\config.toml
Enter password:
Confirm password:
Configuration for adapter 'ALM_Demo-ado' was saved successfully.
Running connection test for 'ALM_Demo-ado'...
Connection test passed for 'ALM_Demo-ado' (pipeline: 'ALM_Demo-S21').

Once the test repository is configured and the connection test succeeds:

1. Finish any remaining agent setup for the pipeline (RFC, pipeline, additional test repositories) if you have not already.
2. Schedule repository search with search_testrepo.
3. Capture coverage with Footprints and your test runs.

For the full setup order, see Start the ABAP Agent Server and Configure Test Repositories.

search_testrepo registers a Windows Scheduled Task that runs watcher.exe SEARCH_TESTREPO on a cron schedule.

Command Prompt

Schedule a search

slabapcli.exe search_testrepo run --pipeline <pipeline> --testrepo <name> [--cron "<cron>"]

PowerShell

Schedule a search

.\slabapcli.exe search_testrepo run --pipeline <pipeline> --testrepo <name> [--cron '<cron>']

Parameter	Required	Description
--pipeline	Yes	Pipeline name ([[pipeline]].name).
--testrepo	Yes	Test repository name ([[testrepo]].name) linked to that pipeline.
--cron	No	5-field cron expression. Default: 0 2 * * 0 (Sunday at 02:00).

Full command reference (stop, list, prerequisites): Search Test Repositories.

SeaLights associates test executions with ABAP code changes through Footprints on the agent side.

1

Schedule Footprints for the pipeline

slabapcli.exe footprints run --pipeline <pipeline-name>

This creates a FOOTPRINTS scheduled task that periodically collects coverage-related data and sends it to SeaLights. Full syntax and stop command: Collect Footprints data for your Pipeline.

2

Run tests against the QAS system

Execute tests that exercise the ABAP components you care about while Footprints is collecting. The agent matches executed ABAP components against objects in the latest Build Modification and reports them as footprints.

3

Wait for processing, then check the Coverage Report

SeaLights needs time to process Footprints data. When processing completes, covered ABAP components appear in your application's Coverage Report.