Ctrlk
Contact SupportProduct
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Validate Your Pipeline Setup

After creating your Initial Build Map, you can validate that your pipeline is correctly configured end-to-end before enabling continuous build modification monitoring. This is done by manually triggering a build modification for a specific transport, letting you confirm that SeaLights detects the code change and displays it correctly in the Coverage Dashboard.

Prerequisites

Before proceeding, confirm that your Initial Build Map is complete and visible in the SeaLights Coverage Dashboard. See Create an Initial Build Map for your Pipeline.

Step 1: Choose a Transport

Select a transport number from your QAS system that:

  • Has already been imported into the QAS system — only imported transports can be reported to SeaLights.

  • Contains code changes you know how to test.

  • Has a corresponding test in your testing tool that covers those changed objects.

  • Has not previously been reported to SeaLights — each transport can only be reported once.

Choosing a transport with a known test lets you verify the complete flow: code change detected → visible in SeaLights → covered by a test run.

Step 2: Trigger a Build Modification

Run the following from your PowerShell window:

Triggers a single build modification for a specific transport. Use this to validate your pipeline setup before enabling continuous monitoring with slabapcli buildmods run.

Syntax
watcher.exe BUILD_MODS <pipeline-name> --transport_num <TRANSPORT_NUMBER>
Syntax
.\watcher.exe BUILD_MODS <pipeline-name> --transport_num <TRANSPORT_NUMBER>
Parameter
Required
Description

<pipeline-name>

Yes

The pipeline name (as shown in pipeline list).

--transport_num

Yes

The transport number to process (e.g. EH4K901492).

Example

This command triggers a single build modification for validation purposes only. It does not start continuous monitoring. To enable continuous build modification monitoring, use slabapcli buildmods run.

When you specify a transport number, the agent uses the current time as the build timestamp (not the transport's historical import time). This ensures the build appears at the correct position in the SeaLights dashboard timeline.

Step 3: Verify in SeaLights

Once the command completes, verify the result in the SeaLights Coverage Dashboard:

  1. Open the Build history window for your application.

  2. Confirm the transport appears as a new Build Modification in the format <Transport name>|<Import datetime>.

  3. Select the Build Modification and open the Code Changes tab to verify the modified objects are listed correctly.

Next Steps

With your pipeline validated, complete the following steps to begin collecting coverage data:

  1. Collect Footprints data for your Pipeline — configure the Agent to collect details for test executions in Tosca. 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.

  2. Run your tests — the default configuration automatically manages the test stage. SeaLights will match the executed ABAP components against the Build Modification and report coverage.

  3. Enable continuous monitoring by proceeding to Monitor your Pipeline for Build Modifications.

Step 3 applies to customers moving forward with a full SeaLights deployment. If you are in an evaluation phase, your setup is complete — continuous monitoring can be enabled at any time when you are ready to go live.

PreviousCreate an Initial Build Map for your PipelineNextMonitor your Pipeline for Build Modifications

Last updated

Was this helpful?