chore: update jest

Author: jonnyowenpowell

jest-environment-fail-fast.ts

@@ -0,0 +1,19 @@
+import type { Circus } from '@jest/types';
+import { TestEnvironment } from 'jest-environment-node';
+
+class FailFastEnvironment extends TestEnvironment {
+  failedTest = false;
+
+  async handleTestEvent(event: Circus.Event, state: Circus.State) {
+    if (event.name === 'hook_failure' || event.name === 'test_fn_failure') {
+      this.failedTest = true;
+    } else if (this.failedTest && event.name === 'test_start') {
+      event.test.mode = 'skip';
+    }
+
+    // @ts-ignore
+    if (super.handleTestEvent) await super.handleTestEvent(event, state);
+  }
+}
+
+export default FailFastEnvironment;

jest.config.js

@@ -1,19 +1,16 @@
 module.exports = {
   preset: "ts-jest",
-  testEnvironment: "node",
+  testEnvironment: './jest-environment-fail-fast.ts',
+  testRunner: 'jest-circus/runner',
   testMatch: ["<rootDir>/test/**/*.spec.ts"],
   testTimeout: 900000, // 15 minutes. Must match UPSTREAM_POLLING_CONFIGURATION in test/helpers/kubernetes-upstream.ts
   bail: true,
   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.
+  // 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
-  // https://snyk.slack.com/archives/CLW30N31V/p1602232569018000?thread_ts=1602230753.017500&cid=CLW30N31V
   globals: {
     "ts-jest": {
       isolatedModules: true,