> 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/guides/show-the-value-with-test-cycles.md). # Show the value with Test Cycles This guide is **Part 2** of the ABAP Agent 2.0 onboarding path. Use it after [Setup and installation](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/setup-and-installation.md). Start only after a successful [initial build map](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/create-an-initial-build-map-for-your-pipeline.md) has been reported and you have searched at least one [test repository](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/search-test-repositories.md). It applies to **all supported test repositories**. The SeaLights **Test Cycle** UI is the hub for day-zero / semantic recommendations (manual or tool-executed). For Tosca Cloud **runner integration and TIA** beyond this flow, continue to [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). ## Goal Demonstrate that after real transports land: 1. The agent creates **build modifications** 2. SeaLights produces **Test Recommendations**, **Test Gaps**, and a **Multi App Coverage Report** for a Test Cycle 3. After **footprints** and running a test, gaps / coverage progress update This matches the **semi-integration** model: recommendations from the SeaLights UI, with execution/footprint data reported back when your workflow supports it. Background: [Test Recommendations for Manual Testing](https://docs.sealights.io/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing) and [How SeaLights Builds Test Recommendations for SAP](https://docs.sealights.io/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing/how-sealights-builds-test-recommendations-for-sap). {% hint style="info" %} SeaLights focuses on **change coverage** for the transports in scope — not overall application coverage from the initial build map. {% endhint %} ## Prerequisites * Part 1 complete (initial build map reported successfully, at least one test repository searched) * One or more **transports with known code (or relevant non-code) changes** you can import/process on QAS * Access to SeaLights: **Test Optimization → Test Recommendations** {% stepper %} {% step %} ### Confirm Part 1 is complete Before you continue: * SeaLights shows a **build** for the application * `search_testrepo` can discover tests for your configured repository If any of these are missing, return to [Setup and installation](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/setup-and-installation.md). {% endstep %} {% step %} ### Process specific transports (watcher) Use the watcher so the agent records a **build modification** for a chosen transport. This is the day-zero validation path before (or alongside) continuous monitoring. Triggers a single build modification for a specific transport. Use this to validate your pipeline setup before enabling continuous monitoring with `slabapcli buildmods run`. {% tabs %} {% tab title="Command Prompt" %} {% code title="Syntax" overflow="wrap" %} ```batch watcher.exe BUILD_MODS --transport_num ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Syntax" overflow="wrap" %} ```powershell .\watcher.exe BUILD_MODS --transport_num ``` {% endcode %} {% endtab %} {% endtabs %} | Parameter | Required | Description | | ----------------- | -------- | ---------------------------------------------------- | | `` | Yes | The pipeline name (as shown in `pipeline list`). | | `--transport_num` | Yes | The transport number to process (e.g. `EH4K901492`). | ## Example {% tabs %} {% tab title="Command Prompt" %} {% code title="Command" overflow="wrap" %} ```batch watcher.exe BUILD_MODS "MyApp-Q40" --transport_num "EH4K901492" ``` {% endcode %} {% endtab %} {% tab title="PowerShell" %} {% code title="Command" overflow="wrap" %} ```powershell .\watcher.exe BUILD_MODS 'MyApp-Q40' --transport_num 'EH4K901492' ``` {% endcode %} {% endtab %} {% endtabs %} {% code title="Expected output (PowerShell)" overflow="wrap" lineNumbers="true" %} ```log .\watcher.exe BUILD_MODS 'MyApp-Q40' --transport_num 'EH4K901492' [2026-03-08 14:22:15.102+02:00] [info] Log level: info [2026-03-08 14:22:15.103+02:00] [info] Current ANSI Code Page: 1252 [2026-03-08 14:22:15.103+02:00] [info] Current version: '1.2.0' [2026-03-08 14:22:15.347+02:00] [info] Retrieving the last import of the transport with a transport num 'EH4K901492' from the RFC destination 'Q40' [2026-03-08 14:22:16.891+02:00] [info] Found 1 transports [2026-03-08 14:22:16.892+02:00] [info] Populating 'IMPORTED_OBJECTS' and 'DELETED_OBJS' table [2026-03-08 14:22:17.204+02:00] [info] Table IMPORTED_OBJECTS populated successfully [2026-03-08 14:22:17.205+02:00] [info] Populating IMPORTED_TRANSPORTS table [2026-03-08 14:22:17.318+02:00] [info] Table IMPORTED_TRANSPORTS populated successfully [2026-03-08 14:22:17.319+02:00] [info] Reading TMDIR table [2026-03-08 14:22:18.540+02:00] [info] TMDIR table read successfully. [2026-03-08 14:22:18.541+02:00] [info] Reading TFDIR table [2026-03-08 14:22:19.103+02:00] [info] TFDIR table read successfully. [2026-03-08 14:22:19.104+02:00] [info] Reading TADIR table [2026-03-08 14:22:20.672+02:00] [info] TADIR table read successfully. [2026-03-08 14:22:20.673+02:00] [info] Reading WBCROSSGT table [2026-03-08 14:22:21.890+02:00] [info] WBCROSSGT table read successfully. [2026-03-08 14:22:21.891+02:00] [info] Reading WBCROSSI table [2026-03-08 14:22:22.754+02:00] [info] WBCROSSGI table read successfully. [2026-03-08 14:22:22.755+02:00] [info] Creating table OBJS_DEVCLASSES [2026-03-08 14:22:22.801+02:00] [info] Table OBJS_DEVCLASSES created successfully [2026-03-08 14:22:22.802+02:00] [info] Creating tables TABL_PROG_XREFS, TABL_FUGR_XREFS, TABL_CLAS_XREFS [2026-03-08 14:22:23.114+02:00] [info] Tables TABL_PROG_XREFS, TABL_FUGR_XREFS, TABL_CLAS_XREFS created successfully [2026-03-08 14:22:23.245+02:00] [info] Serializing data for build modifications with the transport num 'EH4K901492' [2026-03-08 14:22:24.012+02:00] [info] Build session for the transport num 'EH4K901492' opened successfully. Session ID: a1b2c3d4-e5f6-7890-abcd-ef1234567890 [2026-03-08 14:22:26.478+02:00] [info] Build mods for the transport num 'EH4K901492', imported at 2026-03-08 12:15:30 created successfully [2026-03-08 14:22:26.891+02:00] [info] Build session 'a1b2c3d4-e5f6-7890-abcd-ef1234567890' closed successfully [2026-03-08 14:22:26.892+02:00] [info] Ping sender stopped. Total time: 00:00:11.790 ``` {% endcode %} {% hint style="warning" %} 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`. {% endhint %} For continuous monitoring after the demo, see [Monitor your Pipeline for Build Modifications](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/monitor-your-pipeline-for-build-modifications.md) (`buildmods run`). For the initial build map workflow, see [Create an Initial Build Map for your Pipeline](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/create-an-initial-build-map-for-your-pipeline.md). Confirm the SeaLights application shows updated builds / modifications for those transports before opening a cycle. {% endstep %} {% step %} ### Create a Test Cycle in SeaLights In SeaLights, open **Test Optimization → Test Recommendations** and create a cycle for your application, environment, stage, and transport scope. For the wizard and related UI, use the product docs: * [Test Recommendations for Manual Testing](https://docs.sealights.io/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing) — overview hub * [Generating Test Recommendations for Manual Testing](https://docs.sealights.io/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing/generating-test-recommendations-for-manual-testing) — create a cycle * [Manual Test Cycle List](https://docs.sealights.io/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing/manual-test-cycle-list) — review past cycles * [Multi-App Coverage Report for Test Cycle](https://docs.sealights.io/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing/multi-app-coverage-report-for-test-cycle) — coverage tracking Every cycle produces three complementary outputs: | Output | Meaning | | ------------------------ | ------------------------------------------------------------------------------------------ | | **Test Recommendations** | Existing tests that cover the changes in scope | | **Test Gaps** | Changed objects with no associated test in the suite | | **Coverage Report** | Multi App Coverage Report for the cycle (change progress; updates as the cycle progresses) | | {% endstep %} | | {% step %} ### Start footprints collection Start (or confirm) footprints collection for the pipeline so execution on QAS can be associated with the SeaLights build. 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 %} {% endstep %} {% step %} ### Run a recommended test and capture coverage 1. Download or copy recommended tests from the cycle (CSV / UI, per the product docs) 2. Run at least one recommended test in **your** test repository (any supported tool — not Tosca-only) 3. Ensure results / footprints can reach SeaLights for your integration level SeaLights associates test executions with ABAP code changes through **Footprints** on the agent side. {% stepper %} {% step %} ## Schedule Footprints for the pipeline ```batch slabapcli.exe footprints run --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](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/collect-footprints-data-for-your-pipeline.md). {% endstep %} {% step %} ## Run tests against the QAS system Execute tests that exercise the ABAP components you care about while Footprints is collecting. The agent matches executed ABAP components against objects in the latest Build Modification and reports them as footprints. {% endstep %} {% step %} ## Wait for processing, then check the Coverage Report SeaLights needs time to process Footprints data. When processing completes, covered ABAP components appear in your application's Coverage Report. {% endstep %} {% endstepper %} Adapter connection notes: [Test Tool Integrations](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations.md). {% endstep %} {% step %} ### Confirm gaps and coverage move Back in SeaLights for the same cycle: * **Test Gaps** should shrink or clear for objects covered by the test you ran (when footprints/results are reported) * The **Multi App Coverage Report** should reflect progress against the changed scope If nothing moves, verify footprints, lab ID / environment alignment, and that the test actually exercised the changed objects — see Troubleshooting below. {% endstep %} {% endstepper %} ## Troubleshooting | Problem | What to check | | --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | No application / build in SeaLights after the initial build map | Check server and watcher logs. Verify RFC connectivity with `slabapcli rfc test --name `. | | `setup status` fails | Fix SeaLights token, RFC destinations, SAP authorizations, and SCMON before starting the server. See [Validate Your Setup](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/command-line-interface/validate-your-setup.md). | | `search_testrepo` finds nothing | Confirm every `testrepo set` for the pipeline is done. If you just changed config, verify it reloaded — see [Configuration Settings](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/configuration-settings.md). Check adapter logs under [Log locations](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/configuration-settings.md#log-locations). For Fiori, confirm FLPCA was imported. | | No coverage / Test Gaps do not move after a test | Confirm Footprints is running (`footprints run`). For Tosca, set **SeaLightsLabId** to the auto-derived pipeline lab ID — leave `--labid` unset on `pipeline set`. Wait for SeaLights to process Footprints. | | Test Cycles look wrong or empty | Overriding `--labid` casually breaks Test Cycles. Leave it unset so the lab ID matches the QAS branch name (`" "`). Use `pipeline list` to confirm. | | TIA does not skip / optimize tests (Tosca Cloud) | Confirm a Build Modification exists for the transport, Footprints are collecting, and SeaLights optimization is enabled on the playlist. See [Run a test in Tosca Cloud](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations/tosca-cloud/run-a-test-in-tosca-cloud.md). | For deeper diagnosis, see [Troubleshooting the ABAP Agent](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/troubleshooting-the-abap-agent.md). ## Done with Part 2 * For ongoing Tosca Cloud **playlist runner + TIA** (beyond day-zero cycle CSVs), go to [Tosca Cloud runner and TIA](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/tosca-cloud-runner-and-tia.md) * For Fiori/OData context specifics, see [Fiori support](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/fiori-support.md) ## Related reading * [Setup and installation](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/guides/setup-and-installation.md) * [Test Recommendations for Manual Testing](https://docs.sealights.io/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing) * [Test Tool Integrations](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/abap-agent-2.0/test-tool-integrations.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/guides/show-the-value-with-test-cycles.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.