Run a test in Tosca Commander
Run Tosca Commander tests with SeaLights lab ID, Footprints coverage, and TIA.
After you connect Tosca Commander and have created a Footprints scheduled task, configure Tosca so each run associates with your SeaLights app's latest Build Modification.
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.
Test-runner integration
Ensure the SeaLights integration is enabled in Tosca Commander (see the Tricentis integration overview).
On the execution list, playlist, or configuration you use for ABAP testing:
SeaLightsLabId in Tosca Commander or Tosca Cloud must match the labid of your ABAP pipeline:
On the agent host, run
pipeline list(no parameters). Syntax and example output: Create and list pipelines.In the output, find the block for your pipeline and note the labid line (for example,
labid : S21 vwsvtstsap13.tricentis.com).Set SeaLightsLabId on your Tosca execution list, playlist, or configuration parameters to that value (without the
labidlabel).Set SeaLightsOptimization = true when you want SeaLights Test Optimization to influence which tests run.
Playlist and configuration parameter names are case sensitive.
Exact screens differ by Tosca Commander version. If a parameter is not visible, follow the Tricentis SeaLights integration guide for your release.
Once the test repository is configured and the connection test succeeds:
Finish any remaining agent setup for the pipeline (RFC, pipeline, additional test repositories) if you have not already.
Schedule repository search with
search_testrepo.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.
--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.
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.
Run the test and verify coverage
Confirm Footprints is scheduled:
slabapcli footprints run --pipeline <pipeline-name>(see Collect Footprints data).Run the Tosca Commander execution that targets your QAS system.
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:
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.
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.
Related
Tosca Cloud — Cloud playlists and TIA
Last updated
Was this helpful?

