[CI/Build] Fail e2e tests when accuracy is 0% #676
Merged
+15
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Description
This PR adds error handling to domain classification, PII detection, and jailbreak detection e2e tests to ensure they fail explicitly when accuracy is 0%.
Motivation
Previously, these tests would return
nil(success) even when all test cases failed, which could mask critical issues in the routing and detection logic. This change makes test failures more visible and actionable by returning a descriptive error whencorrectTests == 0.Changes
testDomainClassify()functiontestPIIDetection()functiontestJailbreakDetection()function"<test-name> test failed: 0% accuracy (0/<total> correct)"Testing
The changes ensure that:
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE
-swhen doinggit commit[Bugfix],[Feat], and[CI].Pull Request opened by Augment Code with guidance from the PR author