Multiple Transports and Code Changes Coverage

When working with SAP systems, it's common to import a set of related changes via multiple transports. This guide explains how SeaLights processes these transports and how you can ensure your Code Changes Coverage accurately reflects the entire scope of your import.

How SeaLights Processes Transports by Default

By default, when you import a set of transports from SAP into your system, SeaLights automatically reports every individual transport as a separate build.

This means that if you import Transport A, then Transport B, and finally Transport C in sequence:

• SeaLights will register Build 1 (for Transport A).

• Then Build 2 (for Transport B).

• Then Build 3 (for Transport C).

Each of these builds, by default, is compared to the immediately preceding build in SeaLights. For example, Build 3 (Transport C) will be compared to Build 2 (Transport B).

The Challenge: Code Changes Coverage for a Full Import

Due to this default behavior, when you look at the latest build on your Coverage Dashboard, the Code Changes Coverage will only include the code changes from that last build – meaning, the changes introduced by the last transport in your import sequence. This might not give you the full picture of all the changes that were part of your entire import operation.

The Solution: Setting a Reference Build for Comprehensive Coverage

To ensure your Code Changes Coverage accurately reflects all code changes across an entire import (which may contain multiple transports), you should set a Reference Build before you begin importing your new set of transports.

By setting a reference build, you instruct SeaLights to compare the final build of your import against a specific, older baseline, thereby capturing all the changes introduced by all transports in that import.

Steps to Set a Reference Build:

1. Before Importing Transports: Navigate to the Coverage Dashboard in your SeaLights application.

2. Identify Your Baseline: Locate the latest build that represents the state of your code before you start importing your new transports. This will be your comparison baseline. The dashboard displays the latest build for all your applications. You can either select this latest build as your reference, or click the build history button (located next to the build name) to open a list of previous builds and select a different one as your baseline.

3. Set as Reference Build: Hover over this specific build in the dashboard's build list. You will see a "Reference Build" button appear (typically a flag icon).

   
4. Confirm: Click the button. A pop-up will appear, allowing you to confirm setting this build as a reference build.

Outcome

Once you have imported all your transports, the latest build reported to SeaLights (which corresponds to your final transport in the sequence) will then compare against this designated Reference Build. This ensures that the Code Changes Coverage displayed on your dashboard accurately reflects the actual coverage of all code changes included in your recent multi-transport import, providing a true cumulative view of your testing efforts for that entire set of changes.