test(stepdefinitionpath): added the relevant mocks back

Author: lgandecki

lib/stepDefinitionPath.test.js

@@ -19,6 +19,7 @@ describe("load path from step definitions", () => {
     getConfig.mockReturnValue({
       nonGlobalStepDefinitions: true
     });
+    fs.existsSync.mockReturnValue(false);
 
     const errorMessage = `We've tried to resolve your step definitions at ${defaultNonGlobalStepDefinitionsPath}, but that doesn't seem to exist. As of version 2.0.0 it's required to set step_definitions in your cypress-cucumber-preprocessor configuration. Look for nonGlobalStepDefinitions and add stepDefinitions right next to it. It should match your cypress configuration has set for integrationFolder. We no longer rely on getting information from that file as it was unreliable and problematic across Linux/MacOS/Windows especially since the config file could have been passed as an argument to cypress.`;
     expect(stepDefinitionPath).throw(errorMessage);
@@ -30,6 +31,7 @@ describe("load path from step definitions", () => {
       nonGlobalStepDefinitions: true,
       stepDefinitions
     });
+    fs.existsSync.mockReturnValue(false);
 
     const errorMessage = `We've tried to resolve your step definitions at ${stepDefinitions}, but that doesn't seem to exist. As of version 2.0.0 it's required to set step_definitions in your cypress-cucumber-preprocessor configuration. Look for nonGlobalStepDefinitions and add stepDefinitions right next to it. It should match your cypress configuration has set for integrationFolder. We no longer rely on getting information from that file as it was unreliable and problematic across Linux/MacOS/Windows especially since the config file could have been passed as an argument to cypress.`;
     expect(stepDefinitionPath).throw(errorMessage);