refactor: rename chrome-path.setup.ts to chrome-path.mock.ts

Author: vmasek

packages/plugin-lighthouse/CONTRIBUTING.md

@@ -15,7 +15,7 @@ To test lighthouse properly we work with a predefined testing setup.
 
 On some OS there could be a problem finding the path to Chrome.
 
-We try to detect it automatically in the [`chrome-path.setup.ts` script](../../testing/test-setup/src/lib/chrome-path.setup.ts).
+We try to detect it automatically in the [`chrome-path.mock.ts` script](../../testing/test-setup/src/lib/chrome-path.mock.ts).
 There we use `getChromePath` and have `chromium` installed as NPM package, so detecting the path should not cause any problem.
 
 However, if no chrome path is detected automatically the error looks like this:
@@ -46,7 +46,7 @@ In the CI you can set a static path if needed over the env variable like this:
 # ...
 ```
 
-We consider this path in our `beforeAll` hook in a [`chrome-path.setup.ts` script](../../testing/test-setup/src/lib/chrome-path.setup.ts).
+We consider this path in our `beforeAll` hook in a [`chrome-path.mock.ts` script](../../testing/test-setup/src/lib/chrome-path.mock.ts).
 
 ### Testing chrome flags
 

packages/plugin-lighthouse/vite.config.integration.ts

@@ -24,7 +24,7 @@ export default defineConfig({
     setupFiles: [
       '../../testing/test-setup/src/lib/cliui.mock.ts',
       '../../testing/test-setup/src/lib/reset.mocks.ts',
-      '../../testing/test-setup/src/lib/chrome-path.setup.ts',
+      '../../testing/test-setup/src/lib/chrome-path.mock.ts',
     ],
   },
 });

packages/plugin-typescript/vite.config.integration.ts

@@ -24,7 +24,7 @@ export default defineConfig({
     setupFiles: [
       '../../testing/test-setup/src/lib/cliui.mock.ts',
       '../../testing/test-setup/src/lib/reset.mocks.ts',
-      '../../testing/test-setup/src/lib/chrome-path.setup.ts',
+      '../../testing/test-setup/src/lib/chrome-path.mock.ts',
     ],
   },
 });