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
- Add a verification step in
.github/workflows/integration_tests.yml that asserts execution of required suites on both tracks.
- Start with
Groups.Integration.Tests.ps1 and expand to a maintained required-suite list.
- 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
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
Suggested approach
.github/workflows/integration_tests.ymlthat asserts execution of required suites on both tracks.Groups.Integration.Tests.ps1and expand to a maintained required-suite list.Related areas
.github/workflows/integration_tests.ymlTests/Integration/Groups.Integration.Tests.ps1