test: fail e2e tests when accuracy is 0%

Add error handling to domain classification, PII detection, and jailbreak
detection tests to ensure they fail explicitly when accuracy is 0%.

Previously, these tests would return nil (success) even when all test cases
failed, which could mask critical issues. Now they return a descriptive error
when correctTests == 0, making test failures more visible and actionable.

Signed-off-by: bitliu <[email protected]>

Author: Xunzhuo

e2e/testcases/domain_classify.go

@@ -92,6 +92,11 @@ func testDomainClassify(ctx context.Context, client *kubernetes.Clientset, opts
 			correctTests, totalTests, accuracy)
 	}
 
+	// Return error if accuracy is 0%
+	if correctTests == 0 {
+		return fmt.Errorf("domain classification test failed: 0%% accuracy (0/%d correct)", totalTests)
+	}
+
 	return nil
 }
 

e2e/testcases/jailbreak_detection.go

@@ -103,6 +103,11 @@ func testJailbreakDetection(ctx context.Context, client *kubernetes.Clientset, o
 			correctTests, totalTests, detectionRate)
 	}
 
+	// Return error if detection rate is 0%
+	if correctTests == 0 {
+		return fmt.Errorf("jailbreak detection test failed: 0%% accuracy (0/%d correct)", totalTests)
+	}
+
 	return nil
 }
 

e2e/testcases/pii_detection.go

@@ -103,6 +103,11 @@ func testPIIDetection(ctx context.Context, client *kubernetes.Clientset, opts pk
 			correctTests, totalTests, detectionRate)
 	}
 
+	// Return error if detection rate is 0%
+	if correctTests == 0 {
+		return fmt.Errorf("PII detection test failed: 0%% accuracy (0/%d correct)", totalTests)
+	}
+
 	return nil
 }