Run a Test in Tosca

After you have created a FOOTPRINTS scheduled task, the next step is to configure Tosca so that when you run a test, the execution is associated with your SeaLights app’s latest Build Modification. You can do this as follows:

Find the Build Session ID of your app’s latest Build Modification

To find the Build Session ID of your app’s latest Build Modification, follow these steps:

1. Select your app in the SeaLights Coverage Dashboard and open its Build history window.

2. Highlight the most recent build and select the Open cockpit build monitor button to open the Cockpit Build Monitor.

3. Locate the Build details pane.

   
4. Select the Copy button next to the Build Session ID field to copy the value to the Clipboard.

Configure Tosca to use the Build Session ID

To configure Tosca to use the Build Session ID, follow these steps:

1. Start Tosca Commander and open your workspace.

2. Expand Execution > ExecutionLists in the hierarchy and select the execution list you want to run.

3. Select the TEST CONFIGURATION tab, and note the value of the SeaLightsBuildSessionIdFilePath configuration setting.

   
4. Navigate to the specified directory, in this example C:\SeaLights.

   • If the specified file exists, replace its contents with the copied Build Session ID.

   • If the specified file doesn’t exist, create the file and paste in the copied Build Session ID.

5. Save the file.

Run the test

You can now run a test in Tosca. If the test executes any ABAP components in the latest Build Modification for your SeaLights app, you’ll see the test coverage in your app’s Coverage Report.

The following Coverage Report for Pipeline HH_SLABAPCLI_170625 shows that Function YCD_GET_MATL_PRICES and Program YCDMAINPROG have code that’s covered by a Tosca test.