For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connect Tosca Commander to SeaLights

Configure Tosca Commander and the ABAP Agent tosca adapter for SeaLights.

This page covers Tosca Commander (type = tosca). For Tosca Cloud, see Connect Tosca Cloud to SeaLights.

When you run a test in Tosca Commander, Tosca can report the execution to SeaLights so coverage maps to ABAP components in your application's latest Build Modification. SeaLights supports Tosca Commander 2025.1.4 (see the Tricentis manuals linked below for the integration package you install in Tosca).

Tosca Commander SeaLights integration (test runner)

Configure the SeaLights integration in Tosca Commander as described in the Tosca documentation:

When you configure a test run or playlist for SeaLights, SeaLightsLabId must match the ABAP Agent pipeline labid.

SeaLightsLabId in Tosca Commander or Tosca Cloud must match the labid of your ABAP pipeline:

  1. On the agent host, run pipeline list (no parameters). Syntax and example output: Create and list pipelines.

  2. In the output, find the block for your pipeline and note the labid line (for example, labid : S21 vwsvtstsap13.tricentis.com).

  3. Set SeaLightsLabId on your Tosca execution list, playlist, or configuration parameters to that value (without the labid label).

UI steps and dialog names can vary by Tosca Commander version. Prefer the Tricentis manuals above for product-side screens; the sections below cover the ABAP Agent adapter.

Configure the ABAP Agent tosca adapter

Create or update a test repository with slabapcli testrepo set --type tosca.

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

Provide exactly one credential pair when prompted: username + password (managed workspaces) or apikey + apisecret (unmanaged workspaces).

testrepo set parameters for tosca

Non-secret keys use --setting key=value. Secrets are entered interactively (not via --setting). Provide exactly one credential pair: username + password, or apikey + apisecret. Plus common options (--name, --type, --pipeline, --test-stage) — see Configure Test Repositories.

Parameter
Kind
Required
Description

url

Setting

Yes

Tosca Commander REST base URL.

project

Setting

Yes

Tosca workspace / project name.

workstates

Setting

No

Comma-separated test case workstates to include; empty = all.

searchTransaction

Setting

No

true / false — search Transactions.

searchTestConfiguration

Setting

No

true / false — UI5 Test Configuration search.

searchTile

Setting

No

true / false — UI5 Tile search.

searchApiTypeSapModule

Setting

No

true / false — UI5 ApiTypeSapModule search.

bufferPatterns

Setting

No

Semicolon-separated patterns; non-empty enables UI5 Buffer search.

parameterPatterns

Setting

No

Semicolon-separated patterns; non-empty enables UI5 Parameter search.

skipCollect

Setting

No

true / false — when true, skip the collect/rank enrichment step.

configurationPatterns

Setting

No

Semicolon-separated patterns for filtering Tosca Test Configurations.

searchPaths

Setting

No

Comma-separated list that scopes the search to specific Tosca paths. Written as top-level searchpaths in config.toml.

confidenceThreshold

Setting

No

Integer 0–100. Minimum confidence for a match.

username

Secret

One credential pair

Tosca username (managed workspace).

password

Secret

One credential pair

Tosca password (managed workspace).

apikey

Secret

One credential pair

Tosca API key (unmanaged workspace).

apisecret

Secret

One credential pair

Tosca API secret (unmanaged workspace).

Global Tosca search defaults live under [adapters.tosca] in Configuration settings.

Example config.toml shape

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.

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

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.

Next step

Continue with Run a test in Tosca Commander for test-runner parameters, Footprints association, and Test Impact Analysis (TIA).

Last updated

Was this helpful?