refactor: rename mock to mocks folders

Author: Szymon.Poltorak

…gins/src/lighthouse/mock/fixtures/lhr.ts …ins/src/lighthouse/mocks/fixtures/lhr.tsexamples/plugins/src/lighthouse/mock/fixtures/lhr.ts renamed to examples/plugins/src/lighthouse/mocks/fixtures/lhr.ts examples/plugins/src/lighthouse/mock/fixtures/lhr.ts renamed to examples/plugins/src/lighthouse/mocks/fixtures/lhr.ts

@@ -14,7 +14,7 @@
       "!{workspaceRoot}/**/.code-pushup/**/*",
       "!{projectRoot}/code-pushup.config.?(m)[jt]s",
       "!{projectRoot}/code-pushup.config.bundled_*.mjs",
-      "!{projectRoot}/@(test|mocks|mock)/**/*",
+      "!{projectRoot}/@(test|mocks)/**/*",
       "!{projectRoot}/**/?(*.)test.[jt]s?(x)?(.snap)",
       "!{projectRoot}/**/?(*.)mocks.[jt]s?(x)",
       "!{projectRoot}/**/?(*.)mock.[jt]s?(x)",

nx.json

@@ -1,6 +1,6 @@
 import { describe, expect, it, vi } from 'vitest';
 import type { UploadConfig } from '@code-pushup/models';
-import { normalizedExecutorContext } from '../../../mock/utils/executor.js';
+import { normalizedExecutorContext } from '../../../mocks/utils/executor.js';
 import * as config from '../internal/config.js';
 import { parseCliExecutorOptions } from './utils.js';
 

packages/nx-plugin/mock/fixtures/env.ts packages/nx-plugin/mocks/fixtures/env.tspackages/nx-plugin/mock/fixtures/env.ts renamed to packages/nx-plugin/mocks/fixtures/env.ts

@@ -1,5 +1,5 @@
 import { describe, expect } from 'vitest';
-import { ENV } from '../../../mock/fixtures/env.js';
+import { ENV } from '../../../mocks/fixtures/env.js';
 import { uploadConfig } from './config.js';
 import * as env from './env.js';
 

packages/nx-plugin/mock/utils/executor.ts …ckages/nx-plugin/mocks/utils/executor.tspackages/nx-plugin/mock/utils/executor.ts renamed to packages/nx-plugin/mocks/utils/executor.ts packages/nx-plugin/mock/utils/executor.ts renamed to packages/nx-plugin/mocks/utils/executor.ts

@@ -1,6 +1,6 @@
 import { type MockInstance, describe, expect } from 'vitest';
 import { osAgnosticPath } from '@code-pushup/test-utils';
-import { ENV } from '../../../mock/fixtures/env.js';
+import { ENV } from '../../../mocks/fixtures/env.js';
 import { globalConfig, persistConfig, uploadConfig } from './config.js';
 
 describe('globalConfig', () => {

packages/nx-plugin/src/executors/cli/utils.int.test.ts

@@ -66,15 +66,15 @@ For a full list of available flags check out [this document](https://peter.sh/ex
 
 ### Chrome User Data
 
-To bootstrap Chrome with a predefined for setting we have to provide a couple of config files that we located under `<project-root>/mock/chromium-user-data`.
+To bootstrap Chrome with a predefined for setting we have to provide a couple of config files that we located under `<project-root>/mocks/chromium-user-data`.
 When executing Lighthouse we provide the path to this folder over the `Flag` object.
 
 To generate initialise or edit the file structure under `chromium-user-data` do the following steps:
 
-1. Spin up Chrome by running `npx chrome-debug --user-data-dir=./packages/plugin-lighthouse/mock/chromium-user-data`
+1. Spin up Chrome by running `npx chrome-debug --user-data-dir=./packages/plugin-lighthouse/mocks/chromium-user-data`
    <img width="1202" alt="chrome-blank-screen" src="./docs/images/chrome-blank-screen.png">
 
-2. If you do this the first time you should already see content under `<project-root>/mock/chromium-user-data`
+2. If you do this the first time you should already see content under `<project-root>/mocks/chromium-user-data`
 3. Edit the configuration over the Chrome UI. E.g. adding a profile
 4. Close chromium and open it again, and you should see chromium bootstraps as the configured user
    <img width="1202" alt="chrome-blank-screen-pre-configured" src="./docs/images/chrome-blank-screen-pre-configure.png">