Executing globalConfig only when there are tests available to be exec…

…uted (#5323)
jestjs · Jan 15, 2018 · 7743c09 · 7743c09
1 parent dd848f3
commit 7743c09
Showing 1 changed file with 4 additions and 5 deletions.
diff --git a/packages/jest-cli/src/run_jest.js b/packages/jest-cli/src/run_jest.js
@@ -95,10 +95,6 @@ export default (async function runJest({
   onComplete: (testResults: AggregatedResult) => any,
   failedTestsCache: ?FailedTestsCache,
 }) {
-  if (globalConfig.globalSetup) {
-    // $FlowFixMe
-    await require(globalConfig.globalSetup)();
-  }
   const sequencer = new TestSequencer();
   let allTests = [];
 
@@ -184,7 +180,10 @@ export default (async function runJest({
   // original value of rootDir. Instead, use the {cwd: Path} property to resolve
   // paths when printing.
   setConfig(contexts, {cwd: process.cwd()});
-
+  if (globalConfig.globalSetup) {
+    // $FlowFixMe
+    await require(globalConfig.globalSetup)();
+  }
   const results = await new TestScheduler(globalConfig, {
     startRun,
   }).scheduleTests(allTests, testWatcher);