> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/tosca/connect-tosca-to-sealights.md).

# Connect Tosca Commander to SeaLights

This page covers **Tosca Commander** (`type = tosca`). For Tosca Cloud, see [Connect Tosca Cloud to SeaLights](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/tosca-cloud/connect-tosca-cloud-to-sealights.md).

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:

* [SeaLights integration overview (Tosca Commander)](https://documentation.tricentis.com/tosca/2510/en/content/sealights_integration/sealights_integration_overview.htm)
* [Optimize your Tosca test run with SeaLights](https://documentation.tricentis.com/tosca/2510/en/content/sealights_integration/sealights_optimization.htm)

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

{% hint style="warning" %}
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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/create-and-list-pipelines.md).
{% endhint %}

**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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/create-and-list-pipelines.md).
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).

{% hint style="info" %}
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.
{% endhint %}

## Configure the ABAP Agent `tosca` adapter

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

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Command" overflow="wrap" %}

```batch
slabapcli.exe testrepo set --name "tosca_repo" --type tosca --pipeline "<pipeline>" --setting url=http://tosca-server.example/rest --setting project=ProjectName --test-stage "Regression Tests"
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Command" overflow="wrap" %}

```powershell
.\slabapcli.exe testrepo set --name 'tosca_repo' --type tosca --pipeline '<pipeline>' --setting url=http://tosca-server.example/rest --setting project=ProjectName --test-stage 'Regression Tests'
```

{% endcode %}
{% endtab %}
{% endtabs %}

`--test-stage` is optional. See [Configure Test Repositories](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/configure-test-repositories.md) 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).

{% code title="Expected output (PowerShell, abbreviated)" overflow="wrap" lineNumbers="true" %}

```log
.\slabapcli.exe testrepo set --name 'tosca_repo' --type tosca --pipeline '<pipeline>' --setting url=http://tosca-server.example/rest --setting project=ProjectName --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 username: user
Confirm username:
Enter password:
Confirm password:
Configuration for adapter 'tosca_repo' was saved successfully.
Running connection test for 'tosca_repo'...
Connection test passed for 'tosca_repo' (pipeline: '<pipeline>').
```

{% endcode %}

### `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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/configure-test-repositories.md).

| 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/configuration-settings.md).

### Example `config.toml` shape

```toml
[[testrepo]]
  name = 'tosca_repo'
  type = 'tosca'
  pipeline = 'my-pipeline'
  searchpaths = [
    'tosca/testrepo/path/to/search',
  ]
  teststage = 'Regression Tests'

[testrepo.settings]
  url = 'http://tosca-server.example/rest'
  project = 'ProjectName'
  workstates = []
  username = 'user'
  password = 'password'
  apikey = ''
  apisecret = ''
  searchTransaction = true
  searchTestConfiguration = false
  searchTile = false
  searchApiTypeSapModule = false
  bufferPatterns = []
  parameterPatterns = []
```

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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/start-the-agent-server.md) and [Configure Test Repositories](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/configure-test-repositories.md).

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

{% tabs %}
{% tab title="Command Prompt" %}
{% code title="Schedule a search" overflow="wrap" %}

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

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Schedule a search" overflow="wrap" %}

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

{% endcode %}
{% endtab %}
{% endtabs %}

| 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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/search-test-repositories.md).

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

{% stepper %}
{% step %}

## Schedule Footprints for the pipeline

```batch
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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/collect-footprints-data-for-your-pipeline.md).
{% endstep %}

{% step %}

## 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.
{% endstep %}

{% step %}

## 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.
{% endstep %}
{% endstepper %}

## Next step

Continue with [Run a test in Tosca Commander](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/tosca/run-a-test-in-tosca.md) for test-runner parameters, Footprints association, and Test Impact Analysis (TIA).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/tosca/connect-tosca-to-sealights.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.