@vitest-agent/mcp 1.1.0 → 1.2.0

package/vendor/vitest-docs/guide/browser/multiple-setups.md

@@ -1,121 +0,0 @@
-# Multiple Setups
-
-You can specify several different browser setups using the [`browser.instances`](/config/browser/instances) option.
-
-The main advantage of using the `browser.instances` over the [test projects](/guide/projects) is improved caching. Every project will use the same Vite server meaning the file transform and [dependency pre-bundling](https://vite.dev/guide/dep-pre-bundling.html) has to happen only once.
-
-## Several Browsers
-
-You can use the `browser.instances` field to specify options for different browsers. For example, if you want to run the same tests in different browsers, the minimal configuration will look like this:
-
-```ts [vitest.config.ts]
-import { defineConfig } from 'vitest/config'
-import { playwright } from '@vitest/browser-playwright'
-
-export default defineConfig({
-  test: {
-    browser: {
-      enabled: true,
-      provider: playwright(),
-      headless: true,
-      instances: [
-        { browser: 'chromium' },
-        { browser: 'firefox' },
-        { browser: 'webkit' },
-      ],
-    },
-  },
-})
-```
-
-## Different Setups
-
-You can also specify different config options independently from the browser (although, the instances _can_ also have `browser` fields):
-
-::: code-group
-```ts [vitest.config.ts]
-import { defineConfig } from 'vitest/config'
-import { playwright } from '@vitest/browser-playwright'
-
-export default defineConfig({
-  test: {
-    browser: {
-      enabled: true,
-      provider: playwright(),
-      headless: true,
-      instances: [
-        {
-          browser: 'chromium',
-          name: 'chromium-1',
-          setupFiles: ['./ratio-setup.ts'],
-          provide: {
-            ratio: 1,
-          },
-        },
-        {
-          browser: 'chromium',
-          name: 'chromium-2',
-          provide: {
-            ratio: 2,
-          },
-        },
-      ],
-    },
-  },
-})
-```
-```ts [example.test.ts]
-import { expect, inject, test } from 'vitest'
-import { globalSetupModifier } from './example.js'
-
-test('ratio works', () => {
-  expect(inject('ratio') * globalSetupModifier).toBe(14)
-})
-```
-:::
-
-In this example Vitest will run all tests in `chromium` browser, but execute a `'./ratio-setup.ts'` file only in the first configuration and inject a different `ratio` value depending on the [`provide` field](/config/provide).
-
-::: warning
-Note that you need to define the custom `name` value if you are using the same browser name because Vitest will assign the `browser` as the project name otherwise.
-:::
-
-## Filtering
-
-You can filter what projects to run with the [`--project` flag](/guide/cli#project). Vitest will automatically assign the browser name as a project name if it is not assigned manually. If the root config already has a name, Vitest will merge them: `custom` -> `custom (browser)`.
-
-```shell
-$ vitest --project=chromium
-```
-
-::: code-group
-```ts{6,8} [default]
-export default defineConfig({
-  test: {
-    browser: {
-      instances: [
-        // name: chromium
-        { browser: 'chromium' },
-        // name: custom
-        { browser: 'firefox', name: 'custom' },
-      ]
-    }
-  }
-})
-```
-```ts{3,7,9} [custom]
-export default defineConfig({
-  test: {
-    name: 'custom',
-    browser: {
-      instances: [
-        // name: custom (chromium)
-        { browser: 'chromium' },
-        // name: manual
-        { browser: 'firefox', name: 'manual' },
-      ]
-    }
-  }
-})
-```
-:::

package/vendor/vitest-docs/guide/browser/trace-view.md

@@ -1,126 +0,0 @@
-# Trace View
-
-Vitest Browser Mode supports generating Playwright's [trace files](https://playwright.dev/docs/trace-viewer#viewing-remote-traces). To enable tracing, you need to set the [`trace`](/config/browser/trace) option in the `test.browser` configuration.
-
-::: warning
-Generating trace files is only available when using the [Playwright provider](/config/browser/playwright).
-:::
-
-::: code-group
-```ts [vitest.config.js]
-import { defineConfig } from 'vitest/config'
-import { playwright } from '@vitest/browser-playwright'
-
-export default defineConfig({
-  test: {
-    browser: {
-      provider: playwright(),
-      trace: 'on',
-    },
-  },
-})
-```
-```bash [CLI]
-vitest --browser.trace=on
-```
-:::
-
-By default, Vitest will generate a trace file for each test. You can also configure it to only generate traces on test failures by setting `trace` to `'on-first-retry'`, `'on-all-retries'` or `'retain-on-failure'`. The files will be saved in `__traces__` folder next to your test files. The name of the trace includes the project name, the test name, the [`repeats`](/api/test#repeats) count and [`retry`](/api/test#retry) count:
-
-```
-chromium-my-test-0-0.trace.zip
-^^^^^^^^ project name
-         ^^^^^^ test name
-                ^ repeat count
-                  ^ retry count
-```
-
-To change the output directory, you can set the `tracesDir` option in the `test.browser.trace` configuration. This way all traces will be stored in the same directory, grouped by the test file.
-
-```ts [vitest.config.js]
-import { defineConfig } from 'vitest/config'
-import { playwright } from '@vitest/browser-playwright'
-
-export default defineConfig({
-  test: {
-    browser: {
-      provider: playwright(),
-      trace: {
-        mode: 'on',
-        // the path is relative to the root of the project
-        tracesDir: './playwright-traces',
-      },
-    },
-  },
-})
-```
-
-The traces are available in reporters as [annotations](/guide/test-annotations). For example, in the HTML reporter, you can find the link to the trace file in the test details.
-
-## Trace markers
-
-You can add explicit named markers to make the trace timeline easier to read:
-
-```ts
-import { page } from 'vitest/browser'
-
-document.body.innerHTML = `
-  <button type="button">Sign in</button>
-`
-
-await page.getByRole('button', { name: 'Sign in' }).mark('sign in button rendered')
-```
-
-Both `page.mark(name)` and `locator.mark(name)` are available.
-
-You can also group multiple operations under one marker with `page.mark(name, callback)`:
-
-```ts
-await page.mark('sign in flow', async () => {
-  await page.getByRole('textbox', { name: 'Email' }).fill('john@example.com')
-  await page.getByRole('textbox', { name: 'Password' }).fill('secret')
-  await page.getByRole('button', { name: 'Sign in' }).click()
-})
-```
-
-You can also wrap reusable helpers with [`vi.defineHelper()`](/api/vi#vi-defineHelper) so trace entries point to where the helper is called, not its internals:
-
-```ts
-import { vi } from 'vitest'
-import { page } from 'vitest/browser'
-
-const myRender = vi.defineHelper(async (content: string) => {
-  document.body.innerHTML = content
-  await page.elementLocator(document.body).mark('render helper')
-})
-
-test('renders content', async () => {
-  await myRender('<button>Hello</button>') // trace points to this line
-})
-```
-
-## Preview
-
-To open the trace file, you can use the Playwright Trace Viewer. Run the following command in your terminal:
-
-```bash
-npx playwright show-trace "path-to-trace-file"
-```
-
-This will start the Trace Viewer and load the specified trace file.
-
-Alternatively, you can open the Trace Viewer in your browser at https://trace.playwright.dev and upload the trace file there.
-
-<img alt="Trace Viewer showing the trace timeline and rendered component" img-light src="/trace-viewer-light.png">
-<img alt="Trace Viewer showing the trace timeline and rendered component" img-dark src="/trace-viewer-dark.png">
-
-## Source Location
-
-When you open a trace, you'll notice that Vitest groups browser interactions and links them back to the exact line in your test that triggered them. This happens automatically for:
-
-- `expect.element(...)` assertions
-- Interactive actions like `click`, `fill`, `type`, `hover`, `selectOptions`, `upload`, `dragAndDrop`, `tab`, `keyboard`, `wheel`, and screenshots
-
-Under the hood, Playwright still records its own low-level action events as usual. Vitest wraps them with source-location groups so you can jump straight from the trace timeline to the relevant line in your test.
-
-For anything not covered automatically, you can use `page.mark()` or `locator.mark()` to add your own trace groups — see [Trace markers](#trace-markers) above.