fixup!: update snapshots

Author: JakobJingleheimer

test/fixtures/test-runner/output/dot_reporter.snapshot

@@ -1,7 +1,8 @@
-..XX...X..XXX.X.....
-XXX............X....
-.....X...XXX.XX.....
-XXXXXXX...XXXXX
+........XX...X..XXX.
+X.....XXX...........
+.X.........X...XXX.X
+X.....XXXXXXX...XXXX
+X
 
 Failed tests:
 

test/fixtures/test-runner/output/junit_reporter.snapshot

@@ -1,5 +1,15 @@
 <?xml version="1.0" encoding="utf-8"?>
 <testsuites>
+	<testcase name="sync expect fail (method)" time="*" classname="test" file="*"/>
+	<testcase name="sync expect fail (options)" time="*" classname="test" file="*"/>
+	<testcase name="async expect fail (method)" time="*" classname="test" file="*"/>
+	<testcase name="async expect fail (options)" time="*" classname="test" file="*"/>
+	<testcase name="sync todo with expect fail" time="*" classname="test" file="*">
+		<skipped type="todo" message="true"/>
+	</testcase>
+	<testcase name="sync skip expect fail" time="*" classname="test" file="*">
+		<skipped type="skipped" message="true"/>
+	</testcase>
 	<testcase name="sync pass todo" time="*" classname="test" file="*">
 		<skipped type="todo" message="true"/>
 	</testcase>
@@ -508,19 +518,19 @@ Error [ERR_TEST_FAILURE]: test could not be started because its parent finished
 }
 		</failure>
 	</testcase>
-	<!-- Error: Test "unhandled rejection - passes but warns" at test/fixtures/test-runner/output/output.js:72:1 generated asynchronous activity after the test ended. This activity created the error "Error: rejected from unhandled rejection fail" and would have caused the test to fail, but instead triggered an unhandledRejection event. -->
-	<!-- Error: Test "async unhandled rejection - passes but warns" at test/fixtures/test-runner/output/output.js:76:1 generated asynchronous activity after the test ended. This activity created the error "Error: rejected from async unhandled rejection fail" and would have caused the test to fail, but instead triggered an unhandledRejection event. -->
+	<!-- Error: Test "unhandled rejection - passes but warns" at test/fixtures/test-runner/output/output.js:96:1 generated asynchronous activity after the test ended. This activity created the error "Error: rejected from unhandled rejection fail" and would have caused the test to fail, but instead triggered an unhandledRejection event. -->
+	<!-- Error: Test "async unhandled rejection - passes but warns" at test/fixtures/test-runner/output/output.js:100:1 generated asynchronous activity after the test ended. This activity created the error "Error: rejected from async unhandled rejection fail" and would have caused the test to fail, but instead triggered an unhandledRejection event. -->
 	<!-- Error: A resource generated asynchronous activity after the test ended. This activity created the error "Error: uncaught from outside of a test" which triggered an uncaughtException event, caught by the test runner. -->
-	<!-- Error: Test "immediate throw - passes but warns" at test/fixtures/test-runner/output/output.js:80:1 generated asynchronous activity after the test ended. This activity created the error "Error: thrown from immediate throw fail" and would have caused the test to fail, but instead triggered an uncaughtException event. -->
-	<!-- Error: Test "immediate reject - passes but warns" at test/fixtures/test-runner/output/output.js:86:1 generated asynchronous activity after the test ended. This activity created the error "Error: rejected from immediate reject fail" and would have caused the test to fail, but instead triggered an unhandledRejection event. -->
-	<!-- Error: Test "callback called twice in different ticks" at test/fixtures/test-runner/output/output.js:251:1 generated asynchronous activity after the test ended. This activity created the error "Error [ERR_TEST_FAILURE]: callback invoked multiple times" and would have caused the test to fail, but instead triggered an uncaughtException event. -->
-	<!-- Error: Test "callback async throw after done" at test/fixtures/test-runner/output/output.js:269:1 generated asynchronous activity after the test ended. This activity created the error "Error: thrown from callback async throw after done" and would have caused the test to fail, but instead triggered an uncaughtException event. -->
-	<!-- tests 75 -->
+	<!-- Error: Test "immediate throw - passes but warns" at test/fixtures/test-runner/output/output.js:104:1 generated asynchronous activity after the test ended. This activity created the error "Error: thrown from immediate throw fail" and would have caused the test to fail, but instead triggered an uncaughtException event. -->
+	<!-- Error: Test "immediate reject - passes but warns" at test/fixtures/test-runner/output/output.js:110:1 generated asynchronous activity after the test ended. This activity created the error "Error: rejected from immediate reject fail" and would have caused the test to fail, but instead triggered an unhandledRejection event. -->
+	<!-- Error: Test "callback called twice in different ticks" at test/fixtures/test-runner/output/output.js:275:1 generated asynchronous activity after the test ended. This activity created the error "Error [ERR_TEST_FAILURE]: callback invoked multiple times" and would have caused the test to fail, but instead triggered an uncaughtException event. -->
+	<!-- Error: Test "callback async throw after done" at test/fixtures/test-runner/output/output.js:293:1 generated asynchronous activity after the test ended. This activity created the error "Error: thrown from callback async throw after done" and would have caused the test to fail, but instead triggered an uncaughtException event. -->
+	<!-- tests 81 -->
 	<!-- suites 0 -->
-	<!-- pass 36 -->
+	<!-- pass 40 -->
 	<!-- fail 24 -->
 	<!-- cancelled 2 -->
-	<!-- skipped 9 -->
-	<!-- todo 4 -->
+	<!-- skipped 10 -->
+	<!-- todo 5 -->
 	<!-- duration_ms * -->
 </testsuites>