> 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-cloud/run-a-test-in-tosca-cloud.md). # Run a test in Tosca Cloud Operational order for Tosca Cloud playlists with SeaLights: 1. Start footprints and keep them running 2. Enable TIA 3. Configure the playlist and run the test Adapter setup (if needed): [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). {% 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 ` `. 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 %} ## 1. Start footprints collection Start footprints for the pipeline before you enable TIA or run a playlist. Leave the task running throughout. 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 ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Syntax" overflow="wrap" %} ```powershell .\slabapcli.exe footprints run --pipeline ``` {% 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 ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Stop command" overflow="wrap" %} ```powershell .\slabapcli.exe footprints stop --pipeline ``` {% 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). ## 2. Enable TIA With footprints still collecting: 1. In SeaLights, enable **Test Optimization** for your application. 2. On the playlist **Configuration → Parameters**, set **SeaLightsOptimization** = **true**. {% hint style="danger" %} Playlist parameter names are **case sensitive**. {% endhint %} Tricentis UI: [Optimize with SeaLights (Tosca Cloud)](https://documentation.tricentis.com/tricentis_cloud/en/content/admin_guide/sealights_integration.htm?Highlight=sealights#optimize_sealights). ## 3. Configure the playlist and run Still with footprints collecting: 1. In Tosca Cloud **Integrations → SeaLights**, enter the SeaLights Agent Token ([SeaLights integration](https://documentation.tricentis.com/tricentis_cloud/en/content/admin_guide/sealights_integration.htm)). 2. On the playlist: **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).
Tosca Cloud playlist configuration showing SeaLightsLabId parameter.

Set SeaLightsLabId to the pipeline lab ID.

3. Run the playlist against your QAS system. 4. Wait for SeaLights to process Footprints data, then open the Coverage Report / **Test Optimization** view for your application. {% hint style="info" %} SeaLights needs time to process Footprints data before coverage updates appear. {% endhint %}
SeaLights Coverage Report showing covered ABAP components.
Keep `search_testrepo` scheduled so recommendations stay aligned with Cloud tests — see [Search Test Repositories](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/search-test-repositories.md). ## Related * [Tosca Cloud runner and TIA](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/tosca-cloud-runner-and-tia.md) (Part 3) * [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) * [Tosca Commander](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/tosca.md) --- # 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-cloud/run-a-test-in-tosca-cloud.md?ask=&goal= ``` `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.