[tests] better debug data on failures

HaxeFoundation · Jan 3, 2024 · f9a8a0b · f9a8a0b
1 parent 8ab7572
commit f9a8a0b
Showing 1 changed file with 13 additions and 2 deletions.
diff --git a/tests/server/src/cases/CsSafeTypeBuilding.hx b/tests/server/src/cases/CsSafeTypeBuilding.hx
@@ -23,13 +23,20 @@ class CsSafeTypeBuilding extends TestCase {
 	}
 
 	#if debug
+	var failed:Bool;
 	function _assertHasPrint(s:String, ?pos:haxe.PosInfos) {
-		if (!assertHasPrint(s)) haxe.Log.trace("Fail", pos);
+		if (!assertHasPrint(s)) {
+			failed = true;
+			haxe.Log.trace("Fail: doesn't contain \"" + s + "\"", pos);
+		}
 	}
 	#end
 
 	function assertResult(target:String) {
-		#if debug var assertHasPrint = _assertHasPrint; #end
+		#if debug
+		failed = false;
+		var assertHasPrint = _assertHasPrint;
+		#end
 		assertSuccess();
 
 		// Make sure all types are generated
@@ -40,6 +47,10 @@ class CsSafeTypeBuilding extends TestCase {
 		assertHasPrint("[runtime] Hello from Foo__Main__Main");
 		assertHasPrint("[runtime] Hello from Main");
 
+		#if debug
+		if (failed) messages.filter(m -> StringTools.startsWith(m, "Haxe print: ")).iter(m -> trace(m));
+		#end
+
 		// Disabled this check because types move around a bit so we get false negatives
 		// Kept for debugging purposes
 		if (false && target == "js") {