Manual Test Cycle List

The feature is available exclusively to SAP customers.

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:

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

Cycles are purged after 1 year. Download CSVs from important cycles before they expire.

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.

If a cycle was just created and analysis is still running, the panel will show a loading state. Results appear once processing is complete.

Exported CSV Format

Test Recommendations CSV:

Column	Description
App Area	Functional module (e.g., Finance, HR).
Test Name	Name of the test case.
Execution	The business context, the specific process flow the test covers (e.g., Order-to-Cash).
Execution Type	The type or category of the test execution.
Object Name	The modified SAP object covered by this test.
Object Type	The ABAP type identifier of the SAP object (e.g., METH, ENHO).
Non-Code Name	The name of the non-code object, populated only when applicable.
Non-Code Type	The type of the non-code object, populated only when applicable.

Test Gaps CSV:

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

A test case linked to multiple objects will appear as a separate row for each, preserving full traceability.

---

FAQ

Can I rename or delete a cycle?

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

What does "Running..." in the Closed column mean?

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

Can I filter by Application or Test Stage?

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

What does the "Non-Code Object" column contain?

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