Project analytics scope

Define which SeaLights apps, repositories, and test stages are in scope for published analytics.

Define which SeaLights coverage data appears in published analytics. This scope drives the data sent to Jira, Azure DevOps, and Confluence.

Scope model

Project analytics scope is defined by four settings areas:

• coverage_app_list — which SeaLights apps and branches to query.
• repo_list — how repositories map to those apps and branches.
• test_stages — which raw SeaLights stages appear in the output.
• grouped_test_stages — how several stages roll up into higher-level views.

Which section answers which question

• Which SeaLights apps and branches should the report pull from? — use Coverage app list.
• How do repositories map to SeaLights apps and branches? — use Repository list.
• Which raw test stages should appear in the output? — use Test stages.
• How do I create rolled-up coverage views like overall coverage? — use Grouped test stages.

How these settings work together

1

Define coverage sources

coverage_app_list defines where coverage is collected from.

2

Map repositories

repo_list connects repositories to the correct SeaLights apps and branches.

3

Choose raw stages

test_stages defines the stage-level metrics in the output.

4

Create rollups

grouped_test_stages creates rollups like overall for target systems.

Coverage app list

Use coverage_app_list to match SeaLights application names and branches.

{
  "coverage_app_list": [
    {
      "app_regex": "my-app",
      "branch_regex": "main",
      "integration_build": false
    },
    {
      "app_regex": "my-integration-build",
      "branch_regex": "develop",
      "integration_build": true
    }
  ]
}

Key fields

• app_regex — required SeaLights app matcher.
• branch_regex — required SeaLights branch matcher.
• integration_build — optional integration-build toggle.

Repository list

Use repo_list to map repositories to SeaLights apps.

{
  "repo_list": [
    {
      "repoName": "frontend-app",
      "baseUrl": "[e-mail]:mycompany/",
      "branchName": "main",
      "SealightsAppName": "frontend",
      "SealightsBranchName": "main",
      "ignore": false
    }
  ]
}

Key fields

• repoName — required repository name.
• baseUrl — required git base URL.
• branchName — required repository branch.
• SealightsAppName — required SeaLights app name.
• SealightsBranchName — required SeaLights branch name.
• ignore — optional skip flag.

Test stages

Use test_stages to define the raw stages from SeaLights.

{
  "test_stages": [
    {
      "name": "Unit_Tests",
      "reportJsonKey": "unit_tests",
      "reportTitle": "Unit Tests"
    },
    {
      "name": "Integration_Tests",
      "reportJsonKey": "integration_tests",
      "reportTitle": "Integration Tests"
    }
  ]
}

Key fields

• name — stage name from the SeaLights report.
• reportJsonKey — JSON key in generated output.
• reportTitle — display name in reports.

Grouped test stages

Use grouped_test_stages to aggregate several stages.

{
  "grouped_test_stages": [
    {
      "name": "Overall",
      "reportJsonKey": "overall",
      "reportTitle": "Overall Coverage",
      "stages": ["Unit_Tests", "Integration_Tests", "E2E_Tests"],
      "show_gate": true,
      "severity": 2
    }
  ]
}

Key fields

• name — group identifier.
• reportJsonKey — JSON key for the grouped result.
• reportTitle — display name.
• stages — stage names included in the group.
• show_gate — optional gate display.
• severity — optional gate severity.

Scope design tips

• Start with exact names before using broad regex.
• Keep repository, branch, and SeaLights names aligned.
• Use grouped stages for higher-level summaries.
• Use integration_build: true only for real integration-build flows.

Use Deployment patterns for scope examples and FAQ for repository and test stage questions.