> 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/manual-test-cycle-list.md).

# Manual Test Cycle List

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

The Manual Test Cycle List is the central workspace for reviewing all test recommendation requests generated for an SAP account. Every cycle created via the wizard appears here as a numbered, timestamped entry, providing a full audit trail and the entry point for viewing results, downloading CSVs, and accessing the linked coverage report.

The page is accessed via **Test Optimization → Test Recommendations** in the main navigation, visible only to SAP customers.

***

### Business Value & Key Use Cases

* **QA coordinators** scan the history of recommendation requests to understand how testing scope has shifted across releases.
* **Test managers** open historical cycles to review or re-export recommendations and test gaps without regenerating them.
* **Audit and compliance teams** have a time-stamped record of which tests were recommended for each transport batch over the past year.

***

### Cycle List Table

Each row represents one Test Cycle, showing:

<table data-search="false"><thead><tr><th width="166.61328125">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Cycle Name</strong></td><td>Auto-assigned sequentially (e.g., Cycle 1, Cycle 2).</td></tr><tr><td><strong>By</strong></td><td>The team member who created the cycle.</td></tr><tr><td><strong>Created</strong></td><td>Date the cycle was created.</td></tr><tr><td><strong>Closed</strong></td><td>Date the cycle was closed, or <strong>Running...</strong> if still active.</td></tr><tr><td><strong>Application</strong></td><td>The SAP landscape targeted by the cycle.</td></tr><tr><td><strong>Test Environment</strong></td><td>The test system used.</td></tr><tr><td><strong>Test Stage</strong></td><td>The testing phase (e.g., UAT, Regression, SIT).</td></tr><tr><td><strong>Builds</strong></td><td>Number of transports in scope. For Carry Over cycles, includes transports from the source cycle.</td></tr><tr><td><strong>Coverage Report</strong></td><td>Opens the linked coverage report for this cycle.</td></tr></tbody></table>

{% hint style="warning" %}
**Cycles are purged after 1 year.** Download CSVs from important cycles before they expire.
{% endhint %}

### Recommendation Details - Side Panel

Clicking a cycle row opens a panel showing the full details for that cycle: the scope it was configured with, and the two output tabs:

**Tests to Run:** the recommended test cases to execute, with a download button for the CSV.

**Test Gaps:** the modified SAP objects not covered by any existing test case, with a download button for the CSV.

{% hint style="info" %}
If a cycle was just created and analysis is still running, the panel will show a loading state. Results appear once processing is complete.
{% endhint %}

### Exported CSV Format

**Test Recommendations CSV:**

<table data-search="false"><thead><tr><th width="169.3046875">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>App Area</strong></td><td>Functional module (e.g., Finance, HR).</td></tr><tr><td><strong>Test Name</strong></td><td>Name of the test case.</td></tr><tr><td><strong>Execution</strong></td><td>The business context, the specific process flow the test covers (e.g., Order-to-Cash).</td></tr><tr><td><strong>Execution Type</strong></td><td>The type or category of the test execution.</td></tr><tr><td><strong>Object Name</strong></td><td>The modified SAP object covered by this test.</td></tr><tr><td><strong>Object Type</strong></td><td>The ABAP type identifier of the SAP object (e.g., METH, ENHO).</td></tr><tr><td><strong>Non-Code Name</strong></td><td>The name of the non-code object, populated only when applicable.</td></tr><tr><td><strong>Non-Code Type</strong></td><td>The type of the non-code object, populated only when applicable.</td></tr></tbody></table>

**Test Gaps CSV:**

Same structure as above, without the **Test Name** column, since gaps represent objects with no associated test case.

{% hint style="info" %}
A test case linked to multiple objects will appear as a separate row for each, preserving full traceability.
{% endhint %}

***

### FAQ

<details>

<summary><strong>Can I rename or delete a cycle?</strong></summary>

No. Cycle names are auto-assigned and cannot be edited. Cycles cannot be deleted manually — they expire after 1 year.

</details>

<details>

<summary><strong>What does "Running..." in the Closed column mean?</strong> </summary>

The cycle is still active. Only one cycle can be active at a time - closing happens automatically when a new cycle is created.

</details>

<details>

<summary><strong>Can I filter by Application or Test Stage?</strong></summary>

Not in this version. Filtering is limited to Cycle Name via the search bar.

</details>

<details>

<summary><strong>What does the "Non-Code Object" column contain?</strong> </summary>

SAP transport objects that are not SAP code - for example, configuration entries or metadata. Left blank for standard code objects.

</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/manual-test-cycle-list.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.