test: jest fail-fast when any test fails

Author: ivanstanev

jest.config.js

@@ -7,6 +7,9 @@ module.exports = {
   clearMocks: true,
   errorOnDeprecated: true,
 
+  /** https://github.com/facebook/jest/issues/2867#issuecomment-546592968 */
+  setupFilesAfterEnv: ["./jest.setup-after-env.js"],
+
   // TODO: This is here until a bug in Jest (which in turn affects ts-jest) is resolved.
   // It affects our CI/CD runs and makes the machine run out of memory.
   // https://github.com/facebook/jest/issues/10550

jest.setup-after-env.js

@@ -0,0 +1,4 @@
+const failFast = require("jasmine-fail-fast");
+
+const jasmineEnv = jasmine.getEnv();
+jasmineEnv.addReporter(failFast.init());

package-lock.json

@@ -69,6 +69,7 @@
     "eslint-config-prettier": "^8.3.0",
     "eslint-plugin-prettier": "^3.4.1",
     "fadge": "^0.0.1",
+    "jasmine-fail-fast": "^2.0.1",
     "jest": "^26.6.3",
     "nock": "^13.0.11",
     "prettier": "^2.4.1",

package.json

@@ -29,9 +29,10 @@ async function teardown(): Promise<void> {
   console.log('Removed "kind" network');
 }
 
-beforeAll(teardown);
 afterAll(teardown);
 
+test('clean up environment on start', teardown);
+
 // Make sure this runs first -- deploying the monitor for the next tests
 test('deploy snyk-monitor', async () => {
   namespace = setup.snykMonitorNamespace();