Skip to content

Enforce required integration-suite execution on Cloud and Server tracks #674

Description

@lipkau

Why

We intentionally kept Groups coverage active on both Cloud and Server to avoid fake-green outcomes. That guardrail should be automated, not manual.

Problem

CI currently does not explicitly fail when required integration suites/tags are skipped or not executed across tracks.

Impact

  • Risk of reduced coverage without immediate visibility
  • Potential regressions escaping when only one environment is effectively validated

Suggested approach

  1. Add a verification step in .github/workflows/integration_tests.yml that asserts execution of required suites on both tracks.
  2. Start with Groups.Integration.Tests.ps1 and expand to a maintained required-suite list.
  3. Fail the workflow when required suites are absent or skipped unexpectedly.

Related areas

  • .github/workflows/integration_tests.yml
  • Tests/Integration/Groups.Integration.Tests.ps1
  • integration result parsing/upload steps

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area:CIBacklogFiled for tracking; not yet scheduledIssue:EnhancementTheme:TestsTest infrastructure / fixture / integration-suite work

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions