test(cli): work around jest not respecting test timeout

sanity-io · Oct 6, 2022 · 0b7070b · 0b7070b
1 parent 316a2ff
commit 0b7070b
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 0 deletions.
diff --git a/packages/@sanity/cli/jest.config.cjs b/packages/@sanity/cli/jest.config.cjs
@@ -10,4 +10,5 @@ module.exports = createJestConfig({
   globalTeardown: '<rootDir>/test/shared/globalTeardown.ts',
   slowTestThreshold: 60000,
   testTimeout: 30000,
+  setupFilesAfterEnv: ['<rootDir>/test/shared/setupAfterEnv.ts'],
 })
diff --git a/packages/@sanity/cli/test/shared/setupAfterEnv.ts b/packages/@sanity/cli/test/shared/setupAfterEnv.ts
@@ -0,0 +1,11 @@
+/**
+ * Jest has a bug where it does not respect the project `testTimeout`:
+ * https://github.com/facebook/jest/issues/9696
+ *
+ * To prevent having to redeclare a timeout for every single tests, we use this as a replacement
+ * (we need a little more leeway on these CLI tests, they are quite slow)
+ */
+
+jest.setTimeout(30000) // 30s
+
+export {}