> 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/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing/generating-test-recommendations-for-manual-testing.md).

# Generating Test Recommendations for Manual Testing

{% hint style="info" %}
The feature is available exclusively to SAP customers.
{% endhint %}

<figure><img src="/files/OLqyAcpeJl7K3I5caV1S" alt="" width="563"><figcaption></figcaption></figure>

This page covers the cycle creation wizard, the flow through which a manual tester defines a testing scope and triggers SeaLights' impact analysis. The wizard runs in a **right-side panel**, launched by clicking **"Create New Cycle"** on the Test Recommendations page. It progresses through three steps: App & Stage, Scope Selection, and Recommendations Generation.

When the wizard closes, the main Cycle List refreshes automatically and the new cycle appears at the top. From there, recommendations and test gaps are accessed via the side panel, see [Manual Test Cycle List](/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing/manual-test-cycle-list.md) for how results are displayed and exported.

***

### Business Outcomes and Use Cases

* **Teams starting a new release cycle** define a clean transport batch and receive a fresh set of recommendations with no dependency on prior history.
* **Teams mid-release with untested items** carry over pending tests from a previous cycle and optionally add new transports on top.
* **Test coordinators** configure scope, trigger generation, and share the exported CSV with testers, all within a two-minute workflow.

***

### Wizard Step 1: App & Stage

All fields use searchable single-choice dropdowns. The **Continue** button remains disabled until all three are selected.

* **Application** - The SAP landscape to analyze.
* **Test Environment** - The target system (equivalent to "Lab" elsewhere in SeaLights).
* **Test Stage** - The testing phase (e.g., UAT, SIT, Regression).

### Wizard Step 2: Scope Selection

Users choose one of two mutually exclusive paths.&#x20;

#### **Option A: Start Clean**

Generates recommendations based only on a new set of transports. No prior cycle data is referenced.

The starting point can be defined in one of two ways:

* **By build**: Select a specific transport from a searchable dropdown. The analysis automatically extends from that transport to the latest available build at generation time.
* **By date**: Select a date. The analysis covers all transports imported from that date onward.

The **Continue** button remains disabled until a starting point is selected.

#### **Option B: Carry Over From Previous Cycle**

Continues from a prior cycle's unresolved items.

* Select a **Source Cycle** from a dropdown showing the cycle name and start date.
* The new cycle inherits all recommendations from the source cycle. Tests marked **Completed** or **Passed** in the source cycle are automatically excluded. Only pending or failed items carry over.
* Optional checkbox: *"Add additional builds on top of the selected cycle"* -when checked, allows supplementing the carry-over with new transports.

### Wizard Step 3: Recommendations Generation

Once scope is confirmed, SeaLights runs the analysis in the background. This may take a couple of minutes. A progress indicator is shown while the system processes the transport scope and maps changes to your test suite.

Once complete, the panel shows the **Tests to Run** and **Test Gaps** tabs with download buttons for each CSV. See [Manual Test Cycle List](/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing/manual-test-cycle-list.md) for the full breakdown of results and export format.

***

### Operational Information

{% hint style="warning" %}
**Creating a new cycle immediately closes the currently active cycle.** \
Inform testers working on the active cycle before proceeding -this is irreversible.
{% endhint %}

{% hint style="info" %}
**"Start Clean" does not carry forward any pending tests from prior cycles.** If unfinished items exist, use Carry Over to avoid losing that context.
{% endhint %}

***

### FAQ

<details>

<summary><strong>Can I close the wizard before triggering generation?</strong> </summary>

Yes. Closing the panel at any point before Step 3 cancels the wizard. No cycle is created.

</details>

<details>

<summary><strong>What if I select the wrong scope in Step 2?</strong></summary>

Use the **Back** button to return and change your selection before confirming. Once Step 3 begins, the scope is locked.

</details>

<details>

<summary><strong>Can I select multiple starting builds in "Start Clean" mode?</strong> </summary>

No. You define a single starting point, either a specific transport or a date, and SeaLights automatically extends the scope to the latest available build at generation time.

</details>

<details>

<summary><strong>What happens if I close the panel while analysis is still running?</strong> </summary>

The cycle is still created in the background. It will appear in the Cycle List once processing completes.

</details>

<details>

<summary><strong>How are "Completed" and "Passed" tests identified for Carry Over exclusion?</strong> </summary>

SeaLights cross-references the source cycle's recommendations against reported test results. Tests with any other status - no result, failed, or pending - are carried over.

</details>

<details>

<summary><strong>Are test stage options customizable?</strong> </summary>

Test Stage options are populated from the stages configured in your SeaLights account.

</details>


---

# 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/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing/generating-test-recommendations-for-manual-testing.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.