> For the complete documentation index, see [llms.txt](https://sealights-docs.tricentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sealights-docs.tricentis.com/setup-and-configuration/test-tool-integrations/tosca/run-a-test-in-tosca.md).

# Run a test in Tosca Commander

Run Tosca Commander tests with SeaLights lab ID, Footprints coverage, and TIA.

After you [connect Tosca Commander](broken://pages/AD78Sh9p33IsyXh4cjaA) and have created a Footprints scheduled task, configure Tosca so each run associates with your SeaLights app's latest Build Modification.

## Test-runner integration

1. Ensure the SeaLights integration is enabled in Tosca Commander (see the Tricentis [integration overview](https://documentation.tricentis.com/tosca/2510/en/content/sealights_integration/sealights_integration_overview.htm)).
2. On the execution list, playlist, or configuration you use for ABAP testing:
3. Set **SeaLightsOptimization** = **true** when you want SeaLights Test Optimization to influence which tests run.

{% hint style="danger" %}
Playlist and configuration parameter names are **case sensitive**.
{% endhint %}

{% hint style="info" %}
Exact screens differ by Tosca Commander version. If a parameter is not visible, follow the Tricentis SeaLights integration guide for your release.
{% endhint %}

## Run the test and verify coverage

1. Confirm Footprints is scheduled: `slabapcli footprints run --pipeline <pipeline-name>` (see [Collect Footprints data](broken://pages/BtrDV52TrGwLRpGXR4Nd)).
2. Run the Tosca Commander execution that targets your QAS system.
3. Wait for SeaLights to process Footprints data, then open the Coverage Report for your application.

If the test executes ABAP components that appear in the latest Build Modification, those components show as covered.

## Test Impact Analysis (TIA)

Use TIA after you have baseline coverage and a working code-to-test mapping from repository search:

{% stepper %}
{% step %}

### Enable Test Optimization in SeaLights

In the SeaLights dashboard for your application, enable **Test Optimization**. SeaLights then recommends only tests impacted by code changes instead of the full suite.
{% endstep %}

{% step %}

### Keep repository search current

Ensure `search_testrepo` is scheduled for your Tosca Commander repository so recommendations stay aligned with the tests in Tosca.
{% endstep %}

{% step %}

### Process a transport (build modification)

Import or process a transport that contains known code changes so the agent creates a Build Modification. See [Monitor your Pipeline for Build Modifications](broken://pages/JZVVGs3ieGcAwmbZ8qqj).
{% endstep %}

{% step %}

### Re-run with SeaLightsOptimization

Run the same Tosca Commander suite again with **SeaLightsLabId** set and **SeaLightsOptimization** = **true**. Observe that only the recommended (impacted) tests execute, then review results on the SeaLights **Test Optimization** screen.

Tricentis also documents optimization here: [Optimize your Tosca test run with SeaLights](https://documentation.tricentis.com/tosca/2510/en/content/sealights_integration/sealights_optimization.htm).
{% endstep %}
{% endstepper %}

## Related

* [Tosca Cloud](broken://pages/ipS7hWsMxAB9qf7Bdg5G) — Cloud playlists and TIA
* [Show the value with Test Cycles](broken://pages/EXMBmOkLCBbhPiWjM2ki)