> 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/guides/tosca-cloud-runner-and-tia.md).

# Tosca Cloud runner and TIA

**Part 3** of the ABAP Agent 2.0 path — **Tosca Cloud only**. Use after [Setup and installation](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/setup-and-installation.md) and preferably [Show the value with Test Cycles](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/show-the-value-with-test-cycles.md).

Goal: playlist **test-runner** reporting plus **Test Impact Analysis (TIA)**, beyond day-zero Test Cycle downloads.

{% stepper %}
{% step %}

### Prerequisites

* Part 1 complete (pipeline, build, `toscacloud` test repository)
* Preferably Part 2 complete (at least one build modification)
* Access to Tosca Cloud and SeaLights for your application
  {% endstep %}

{% step %}

### Start footprints collection

Start footprints for the pipeline **first**, and leave the task running for the rest of this flow.

Configures the agent to collect Footprints data for a pipeline. When you run a test, the agent matches the ABAP components that you executed against objects in the latest Build Modification and sends this data to SeaLights as a Footprint.

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

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

{% endcode %}
{% endtab %}

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

```powershell
.\slabapcli.exe footprints run --pipeline <pipeline-name>
```

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

| Parameter    | Required | Description                                      |
| ------------ | -------- | ------------------------------------------------ |
| `--pipeline` | Yes      | The pipeline name (as shown in `pipeline list`). |

## Example

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

```batch
slabapcli.exe footprints run --pipeline "HH_SLABAPCLI_170625"
```

{% endcode %}
{% endtab %}

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

```powershell
.\slabapcli.exe footprints run --pipeline 'HH_SLABAPCLI_170625'
```

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

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

```log
.\slabapcli.exe footprints run --pipeline 'HH_SLABAPCLI_170625'
[2025-06-18 15:07:58.337+01:00] [info] Current ANSI Code Page: 65001 (UTF-8) (65001)
[2025-06-18 15:07:58.337+01:00] [info] Config pathname: ../config/config.toml
[2025-06-18 15:07:58.341+01:00] [info] resource = footprints. command = run
[2025-06-18 15:07:58.341+01:00] [info] pipline: HH_SLABAPCLI_170625
[2025-06-18 15:07:58.370+01:00] [info] Run scheduled daily. interval = 5m. duration = 1d
[2025-06-18 15:07:58.370+01:00] [info] Total time: 00:00:00.033
```

{% endcode %}

This command creates a FOOTPRINTS scheduled task that runs every five minutes to collect Footprints data and send it to SeaLights.

To stop collecting Footprints data, run:

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

```batch
slabapcli.exe footprints stop --pipeline <pipeline-name>
```

{% endcode %}
{% endtab %}

{% tab title="PowerShell" %}
{% code title="Stop command" overflow="wrap" %}

```powershell
.\slabapcli.exe footprints stop --pipeline <pipeline-name>
```

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

Do not run `footprints stop` until you finish collecting coverage. Reference: [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 %}

### Enable TIA

With footprints still collecting:

1. In SeaLights, enable **Test Optimization** for the application.
2. On the Tosca Cloud playlist, set **SeaLightsOptimization** = **true** (case sensitive).

Product UI details: [Optimize with SeaLights (Tosca Cloud)](https://documentation.tricentis.com/tricentis_cloud/en/content/admin_guide/sealights_integration.htm?Highlight=sealights#optimize_sealights) and [How SeaLights Builds Test Recommendations for SAP](https://docs.sealights.io/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing/how-sealights-builds-test-recommendations-for-sap).
{% endstep %}

{% step %}

### Configure Tosca Cloud and run a test

Still with footprints collecting, finish the adapter / playlist setup and run:

* Adapter and connection: [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)
* Playlist parameters and run/verify steps: [Run a test in Tosca Cloud](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/tosca-cloud/run-a-test-in-tosca-cloud.md)

Set **SeaLightsLabId** to the pipeline lab ID (leave `--labid` unset on `pipeline set`).

{% hint style="warning" %}
**Leave `--labid` unset** when you create a pipeline. The agent derives the lab ID automatically so it matches the QAS **branch name**: `"<SID> <ashost>"` (for example, `S21 vwsvtstsap13.tricentis.com`).

Overriding `--labid` casually breaks **Test Cycles** in SeaLights.
{% endhint %}

The auto-derived lab ID is what SeaLights uses for Test Cycles and Footprints. Only override `--labid` when you deliberately need a different lab ID and understand the Test Cycle impact.
{% endstep %}

{% step %}

### Verify in SeaLights

Open **Test Optimization** for your application and confirm playlist results map to the expected build / build modification and that optimization behaves as configured on later runs.
{% endstep %}
{% endstepper %}

## Related

* [Tosca Cloud](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/tosca-cloud.md)
* [Show the value with Test Cycles](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/show-the-value-with-test-cycles.md)
* [Tosca Commander](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/tosca.md) — Commander path (separate from Cloud)


---

# 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/guides/tosca-cloud-runner-and-tia.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.
