Problem
We currently run the full end-to-end test suite on every PR. This has two costs:
Argos credit burn: we exhaust our monthly screenshot budget before month-end, which blocks releases.
CI wall-clock time: every PR pays the build time of every diagram's tests, degrading DX for contributors and maintainers alike.
Proposed change
Detect which diagram(s) a PR actually touches and run only those e2e tests. If the change touches shared/common code (or we can't confidently scope it), fall back to running the full suite.
A simple heuristic to start: if all changed files live under a single diagram directory (e.g. packages/mermaid/src/diagrams/flowchart/) and no common code is modified, only run the e2e tests for that diagram.
Expected outcome
Have a configuration so the feature for running just a subset of e2e tests can be enabled/disabled.
Argos credits last the full month: we can release on schedule.
Faster CI feedback on diagram-scoped PRs.
Full-suite safety net preserved for cross-cutting changes.
Problem
We currently run the full end-to-end test suite on every PR. This has two costs:
Argos credit burn: we exhaust our monthly screenshot budget before month-end, which blocks releases.
CI wall-clock time: every PR pays the build time of every diagram's tests, degrading DX for contributors and maintainers alike.
Proposed change
Detect which diagram(s) a PR actually touches and run only those e2e tests. If the change touches shared/common code (or we can't confidently scope it), fall back to running the full suite.
A simple heuristic to start: if all changed files live under a single diagram directory (e.g. packages/mermaid/src/diagrams/flowchart/) and no common code is modified, only run the e2e tests for that diagram.
Expected outcome
Have a configuration so the feature for running just a subset of e2e tests can be enabled/disabled.
Argos credits last the full month: we can release on schedule.
Faster CI feedback on diagram-scoped PRs.
Full-suite safety net preserved for cross-cutting changes.