vest 5.4.5 → 5.4.6

package/dist/cjs/vest.development.js

@@ -1259,6 +1259,7 @@ function useWithinActiveOmitWhen() {
     return useOmitted();
 }
 
+// eslint-disable-next-line complexity
 function useVerifyTestRun(testObject, collisionResult = testObject) {
     const testData = VestTest.getData(testObject);
     if (useShouldSkipBasedOnMode(testData)) {
@@ -1686,7 +1687,19 @@ function useRunDoneCallbacks() {
 function useInitVestBus() {
     const VestBus = vestjsRuntime.Bus.useBus();
     on('TEST_COMPLETED', () => { });
-    // on("TEST_RUN_STARTED", () => {});
+    on('TEST_RUN_STARTED', () => {
+        // Bringin this back due to https://github.com/ealush/vest/issues/1157
+        // This is a very pecluiar bug in which we're seeing vest behaving differently between
+        // runs when suite.get() is called.
+        // In the bug we experienced that failing tests were skipped in the second run.
+        // The reason: suite.get() built the failures cache. Calling suite.get() before the test run
+        // made Vest think that the field already had failing tests (even though it was the same test!)
+        // and it skipped the test.
+        // A better solution is to be able to identify each failure to its actual position in the suite
+        // but this requires some rearchitecting within Vest.
+        // This is an easy enough solution - we just reset the cache before the test run, let's hope we don't see
+        // any performance issues.
+    });
     VestBus.on(vestjsRuntime.RuntimeEvents.ISOLATE_PENDING, (isolate) => {
         if (VestTest.is(isolate)) {
             VestTest.setPending(isolate);