> 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/guides/sap/sealights-agents-and-plugins/abap-agent/command-line-interface/validate-your-pipeline-setup.md).

# 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](/knowledgebase/guides/sap/sealights-agents-and-plugins/abap-agent/command-line-interface/create-an-initial-build-map-for-your-pipeline.md).

## 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:

{% hint style="info" %}
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.
{% endhint %}

## 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.

<figure><img src="/files/9qW8rFJogrRwaDlW9bB9" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/obJETbiZL6ni6Xgk3qEQ" alt=""><figcaption></figcaption></figure>

## Next Steps

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

1. [**Collect Footprints data for your Pipeline**](/knowledgebase/guides/sap/sealights-agents-and-plugins/abap-agent/command-line-interface/collect-footprints-data-for-your-pipeline.md) — 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 CTS configuration will automatically manage 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](/knowledgebase/guides/sap/sealights-agents-and-plugins/abap-agent/command-line-interface/monitor-your-pipeline-for-build-modifications.md).

{% hint style="info" %}
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.
{% endhint %}


---

# 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/guides/sap/sealights-agents-and-plugins/abap-agent/command-line-interface/validate-your-pipeline-setup.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.