Build Monitor
The Build Monitor screen provides an integration level view of all data for a reported build and associated test stages. Upon initial selection of a specific build i.e. selecting App, Branch, Build from the drop-down menus, a general build overview screen is shown with several tabs.
Build Session and Build Scan details
The landing page of the build selected will provide the details of the two first commands necessary to report a build to Sealights:
config: generation of the Build Session ID (BSID)
build Scan: agent’s scan analysis of the application bytecode
Test Stage details
View Test Stage-specific data by selecting a Test Stage on the right-hand side of the screen.
The “Executions” Tab
In this tab, you’ll find the details of all the test executions associated and aggregated with the current Test Stage: all these executions have contributed to the duration, coverage and tests counters shown in the Build Monitor or the main dashboard.
When you run the same tests against the same build, the test counters and duration will be aggregated. For example, if you execute two times 10 tests against the same build of your application and report them to Sealights, you’ll see a total number of 20 tests reported in the dashboard and the cockpit and it will appear with 2 executions in this tab.
Each execution will be summarized with the following parameters: status, start and end timestamps, lab ID used for the execution, and the ending cause.
There are 3 possible statuses for a Test stage Execution
Created
Execution was initiated and is still in progress.
Pending Delete
Execution was reported to Sealights as ended but entered in our Backend queue for processing. The execution will not stay in this stage for more than 120 seconds.
ended
Execution was ended and processing completed. All metrics are calculated and made available in Selaights dashboard and Reports.
The ending cause column can have the following values
Agent
Execution was ended by a regular agent command.
API
Execution was ended by a regular API call.
Server - Conflict
Sealights' backend detected new executions opened with parameters conflicting with the current one(s) and closed the older one(s) automatically. For example, when the same LabId is used by a different test stage.
Server - Timeout
When opening the execution via the API a timeout can be provided to end automatically the execution. By default the timeout is 4 hours.
Server - Daily
Every day at 3:00 AM GMT, Selaights backend automatically closes open executions left open for more than 24 hours. Please contact Sealights Support if your tests executions durations are by default running for a longer time.
Sealights Support
Sealights Support department had forced the end of the execution manually (Typically for troubleshooting or ticket resolution purpose).
Advanced
JSON details of agent’s command
For Build scanner and Test Listener tabs, view JSON details of the session parameters mapped from the Agent commands.
Validating Pull Request Integration using the Build Monitor
Pull Request jobs are not shown on the dashboard but they can be reviewed using the Build Monitor (by default PR branches are also hidden).
Last updated
Was this helpful?