Release Notes: AI Healing Comments, Exclude Labels
 |
Enhanced AI Auto-Healing Comments for Smarter Test Recovery
We’ve improved the AI auto-healing comments feature to now include AI evaluation before initiating the healing process. When a test step comment encounters an issue—such as a descriptor mismatch or missing element—our AI analyzes whether the comment can be automatically healed prior to attempting repair.
If the AI determines that healing is feasible, it will provide suggested fixes; otherwise, it explains why the comment cannot be healed, which may be due to an actual bug or the absence of a viable solution. This pre-evaluation prevents unnecessary healing attempts on unrepairable errors, ensuring a more reliable and transparent healing workflow.
By clearly displaying additional diagnostic information in the extra info section, users gain insights into healing possibilities and limitations, helping them focus on genuine bugs and improve test stability.
Captions: AI comments on why it can’t be healed.
Captions: AI comments on why it can be healed.
Exclude Labeled Test Cases During Test Case Mutations
testRigor now supports excluding specific test cases by labels when executing mutation testing through API calls, GitHub Actions or any other CICD tool. Previously, GitHub Actions did not honor exclude label settings, but with this update, test case mutations will skip all test cases marked with excluded labels during API-triggered runs.
This enhancement ensures that only test cases without the excluded labels are considered for mutation testing, providing better control and efficiency in test suite execution. By integrating exclude label filtering with GitHub Actions, teams can streamline mutation testing workflows, reduce unnecessary test executions, and improve overall automation performance.
Caption: Exclude Labels in API payload.
Captions: Exclude Labels report.
