Files

GitHub Actions e6e957d0ed fix: isolate security workflow tests to security shard

Moved "Group B: Security Configuration Workflow" from the integration
suite to the dedicated security suite. These tests require Cerberus
middleware to be enabled, which is only present in the security shard.

Extracted Group B tests to workflow-security.spec.ts
Removed Group B from multi-feature-workflows.spec.ts
Prevents false validation failures in non-security CI environments
Changed 4 files

2026-02-06 06:38:12 +00:00

1.2 KiB

Raw Blame History

Shard Isolation Fix Report

Date: February 6, 2026

Problem

Our testing suite had a mix-up. A specific test file (tests/integration/multi-feature-workflows.spec.ts) contained tests that relied on security settings (Group B). However, these tests were running in an environment where those security settings were disabled. This caused the tests to fail incorrectly, creating "false alarms" in our quality checks.

Solution

We moved the "Group B: Security Configuration Workflow" tests into their own dedicated file: tests/security/workflow-security.spec.ts. This ensures they are completely separate from the general integration tests.

Result

Security Tests: Now properly isolated in the security folder. They will only run in the "Security" test environment where they belong.
Integration Tests: The general workflow tests now run cleanly without failing on missing security features.
Stability: This eliminates the false failures, making our automated testing reliable again.

Verification

We ran the Playwright testing tool against the cleaned-up integration file.

Confirmed: "Group B" is no longer present in the integration workflow.
Passed: All remaining tests in the integration file passed successfully.

1.2 KiB Raw Blame History