[Fix] Astra provider CI fails when focused tests are omitted - #1530
[Fix] Astra provider CI fails when focused tests are omitted#1530zoomote[bot] wants to merge 3 commits into
Conversation
Review statusThis PR was opened by an automated account. A human maintainer must verify the change intent, provenance, and validation before merging. Current step: Resolve the merge conflicts. The review sequence resumes after the branch is mergeable. Review-state labels are managed by this workflow; do not edit them manually. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What changed
openai-native-usage.spec.tsin changed-code mutation runs instead of dropping them when a dot-suffixed direct test also exists.Why this change was made
The mutation gate on #1506 omitted an existing focused usage suite and left provider guard branches under-specified. The feature was merged while the final CI remediation was still being validated, so these fixes are isolated in this follow-up.
Impact
Changed-code mutation testing now exercises all directly related focused suites and passes for the Astra provider changes. Runtime behavior from #1506 is preserved.
Related PRs