> 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/knowledge-base/sealights-for-abap/test-cycles/creating-a-new-test-cycle.md). # Creating a New Test Cycle Creating a test cycle is the action that initiates change impact analysis in SeaLights for ABAP. A three-step wizard — Context, Transports, and Recommendations — collects the minimum information needed to define the analysis scope. Once submitted, SeaLights immediately begins tracing changed objects, building the dependency map, and generating test recommendations. No further configuration is required. *** ### Business Value & Key Use Cases * **Immediate impact analysis** — A cycle can be created and producing results in under five minutes after transports land in a QA system, before any manual triage begins. * **Consistent release process** — The wizard enforces a standard input format across all teams and landscapes, making every cycle comparable and auditable regardless of who created it. * **Continuity across release waves** — The Carry Over option ensures unresolved gaps and pending recommendations are never silently dropped between cycles. *** ### Detailed Functionality #### Step 1 — Testing Context Three fields define the analysis environment:
FieldWhat It Controls
LandscapeThe logical SAP pipeline to analyze (e.g., "Europe Finance"). Populated from connected landscapes.
SystemThe specific SAP instance within that landscape (e.g., QA1, Dev). SeaLights reads executable usage data from this system to build its dependency map.
Test RepositoryThe test management tool to draw recommendations from (e.g., qTest, Tosca). Only tests in this repository are considered for this cycle.
> These three fields are permanent once the cycle is created and cannot be changed afterward. #### Step 2 — Transport Scope This step determines what gets analyzed and whether to start fresh or continue from a previous cycle. **Start Clean** creates a fresh cycle with no inherited context — only the transports defined in the range are included. Use this when beginning a new release wave or sprint. 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. **Carry Over** inherits every unresolved item from a chosen previous cycle — open test gaps and pending recommendations — then adds new transports on top. Use this when continuing work across a sprint boundary or when a previous cycle closed before all gaps were resolved. * Select a **Source Cycle** from a dropdown showing the cycle name and start date. * 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. The transport range itself is defined by either a specific transport ID or a date — all transports imported into the selected system from that point onward are included automatically. No manual transport list to maintain. #### Step 3 — Results Once the wizard is submitted, SeaLights populates all three result tabs automatically: * **Change Analysis** — app areas affected, impacted executables, most-at-risk executables, and changed object count * **Tests to Run** — the covering test list and optimal test sub-set * **Test Gaps** — changed objects with no covering test in the connected repository No further action is needed to generate these outputs. *** ### FAQ **Q: Can I edit the cycle scope after creation?** A: No. Landscape, system, test repository, and transport range are all fixed at the point of creation. To adjust the scope, close the current cycle and create a new one using Carry Over to retain any unresolved items. **Q: Does creating a cycle trigger test execution?** A: No. SeaLights produces recommendations — it does not trigger or schedule test runs. Tests are executed by the team using their existing tools, and results are reported back to SeaLights to update coverage. **Q: What is the difference between the covering test list and the optimal test sub-set?** A: The covering list includes every test that exercises at least one most-at-risk executable. The optimal sub-set is the minimum combination of those tests that still guarantees every most-at-risk executable is covered at least once — nothing redundant, nothing missing. **Q: Can multiple cycles run simultaneously on the same landscape and system?** A: Yes. There is no restriction on concurrent active cycles across the same environment. --- # 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/knowledge-base/sealights-for-abap/test-cycles/creating-a-new-test-cycle.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.