> 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/guides/show-the-value-with-test-cycles.md).

# Show the value with Test Cycles

Show value after setup — watcher transports, Test Cycles, recommendations, gaps, Multi App Coverage Report, and footprints for any supported test repo.

This guide is **Part 2** of the ABAP Agent 2.0 onboarding path. Use it after [Setup and installation](broken://pages/jvmOWRjO10SvuLg7G51U).

Start only after a successful [initial build map](broken://pages/6f4WDLP7ZxZdqhvqwcMb) has been reported and you have searched at least one [test repository](broken://pages/3dzoIdoAGQw91N8Jpn6t).

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](broken://pages/zVhfQlDB3kh3AEmmVE1X) (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](broken://pages/jvmOWRjO10SvuLg7G51U).
{% 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 continuous monitoring.

{% hint style="warning" %}
**Prerequisite:** The Initial Build Map for this pipeline must have completed successfully. Do not run watcher `BUILD_MODS` while `INIT_BUILD_MAP` is still in progress.
{% endhint %}

For continuous monitoring after the demo, see [Monitor your Pipeline for Build Modifications](broken://pages/JZVVGs3ieGcAwmbZ8qqj) (`buildmods run`). For the initial build map workflow, see [Create an Initial Build Map for your Pipeline](broken://pages/6f4WDLP7ZxZdqhvqwcMb).

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.
{% 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

Adapter connection notes: [Test Tool Integrations](broken://pages/X3jEQR7gju1fIaT7v4vC).
{% 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

## Done with Part 2

* For ongoing Tosca Cloud **playlist runner + TIA** (beyond day-zero cycle CSVs), go to [Tosca Cloud runner and TIA](broken://pages/zVhfQlDB3kh3AEmmVE1X)
* For Fiori/OData context specifics, see [Fiori support](broken://pages/ZslbGtlcKtkEs84gV7Iz)

## Related reading

* [Setup and installation](broken://pages/jvmOWRjO10SvuLg7G51U)
* [Test Recommendations for Manual Testing](https://docs.sealights.io/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing)
* [Test Tool Integrations](broken://pages/X3jEQR7gju1fIaT7v4vC)