pulibrary / tigerdata-app / 5b99882b-3756-45f3-bc0c-a4224c82b5a6

94%

main: 94%

Pull #2818

circleci

Refactor CircleCI configuration to isolate test suite JUnit results

This commit refactors the CircleCI pipeline configurations to segment different test suites into distinct jobs and isolate their JUnit XML outputs. This prevents test outcomes from different execution environments (such as local Podman vs. shared remote Mediaflux) from blending together in Test Insights, making triage of environment-specific or flaky tests significantly easier.

Key Changes:
- Segment and isolate JUnit output XML files across test suites:
  - Unit/non-system specs (test job) now output JUnit results to /tmp/rspec/unit.xml.
  - System/browser specs (test_browser job) now output JUnit results to /tmp/rspec/browser.xml.
  - Shared remote Mediaflux integration specs (mflux_ci job) now output JUnit results to /tmp/rspec/mflux_ci.xml.
- Add explicit steps to prepare JUnit directories (mkdir -p /tmp/rspec) and store JUnit reports as named CircleCI workflow artifacts for enhanced visibility.
- Introduce dynamic job aliases (integration_deploy_ci_env for deployment and integration_mflux_shared for shared-state integration testing) in workflows to clearly identify execution environments in UI dashboards.
- Rename workflow build_accept_deploy to build_accept.
- Inject TIGERDATA_TEST_SURFACE: integration_mflux_shared env variable to identify the remote shared Mediaflux test surface in logs.
- Add extensive pipeline configuration comments explaining job segments and how to isolate and trace flaky test occurrences by their distinct JUnit artifact.

0 of 4 branches covered (0.0%)

3310 of 3538 relevant lines covered (93.56%)

623.08 hits per line