Merge branch 'main' into fix/use-monotonic-clock-for-timeout-guard

Author: hi-ogawa

.github/workflows/ci.yml

@@ -70,7 +70,7 @@ jobs:
 
       - name: Get changed files
         id: changed-files
-        uses: tj-actions/changed-files@7dee1b0c1557f278e5c7dc244927139d78c0e22a # v47.0.4
+        uses: tj-actions/changed-files@22103cc46bda19c2b464ffe86db46df6922fd323 # v47.0.5
         with:
           files: |
             docs/**

docs/api/advanced/plugin.md

@@ -11,7 +11,7 @@ This is an advanced API. If you just want to [run tests](/guide/), you probably
 This guide assumes you know how to work with [Vite plugins](https://vite.dev/guide/api-plugin.html).
 :::
 
-Vitest supports a `configureVitest` [plugin](https://vite.dev/guide/api-plugin.html) hook hook since version 3.1.
+Vitest supports a `configureVitest` [plugin](https://vite.dev/guide/api-plugin.html) hook since version 3.1.
 
 ::: code-group
 ```ts [only vitest]

docs/api/browser/react.md

@@ -39,6 +39,8 @@ export function render(
 ): Promise<RenderResult>
 ```
 
+The `render` function records a `react.render` trace mark, visible in the [Trace View](/guide/browser/trace-view).
+
 :::warning
 Note that `render` is asynchronous, unlike in other packages. This is to support [`Suspense`](https://react.dev/reference/react/Suspense) correctly.
 
@@ -154,6 +156,8 @@ This method is a shortcut for `console.log(prettyDOM(baseElement))`. It will pri
 function rerender(ui: React.ReactNode): Promise<void>
 ```
 
+Also records a `react.rerender` trace mark in the [Trace View](/guide/browser/trace-view).
+
 It is better if you test the component that's doing the prop updating to ensure that the props are being updated correctly to avoid relying on implementation details in your tests. That said, if you'd prefer to update the props of a rendered component in your test, this function can be used to update props of the rendered component.
 
 ```jsx
@@ -171,6 +175,8 @@ await rerender(<NumberDisplay number={2} />)
 function unmount(): Promise<void>
 ```
 
+Also records a `react.unmount` trace mark in the [Trace View](/guide/browser/trace-view).
+
 This will cause the rendered component to be unmounted. This is useful for testing what happens when your component is removed from the page (like testing that you don't leave event handlers hanging around causing memory leaks).
 
 ```jsx

docs/api/browser/svelte.md

@@ -12,7 +12,7 @@ import { expect, test } from 'vitest'
 import Component from './Component.svelte'
 
 test('counter button increments the count', async () => {
-  const screen = render(Component, {
+  const screen = await render(Component, {
     initialCount: 1,
   })
 
@@ -39,15 +39,26 @@ export function render<C extends Component>(
   Component: ComponentImport<C>,
   options?: ComponentOptions<C>,
   renderOptions?: SetupOptions
-): RenderResult<C>
+): RenderResult<C> & PromiseLike<RenderResult<C>>
 ```
 
+The `render` function records a `svelte.render` trace mark, visible in the [Trace View](/guide/browser/trace-view).
+
+::: warning
+Synchronous usage of `render` is deprecated and will be removed in the next major version. Please always `await` the result:
+
+```ts
+const screen = render(Component) // [!code --]
+const screen = await render(Component) // [!code ++]
+```
+:::
+
 ### Options
 
 The `render` function supports either options that you can pass down to [`mount`](https://svelte.dev/docs/svelte/imperative-component-api#mount) or props directly:
 
 ```ts
-const screen = render(Component, {
+const screen = await render(Component, {
   props: { // [!code --]
     initialCount: 1, // [!code --]
   }, // [!code --]
@@ -68,7 +79,7 @@ For example, if you are unit testing a `tbody` element, it cannot be a child of
 ```ts
 const table = document.createElement('table')
 
-const screen = render(TableBody, {
+const screen = await render(TableBody, {
   props,
   // ⚠️ appending the element to `body` manually before rendering
   target: document.body.appendChild(table),
@@ -86,7 +97,7 @@ If the `target` is specified, then this defaults to that, otherwise this default
 In addition to documented return value, the `render` function also returns all available [locators](/api/browser/locators) relative to the [`baseElement`](#baseelement), including [custom ones](/api/browser/locators#custom-locators).
 
 ```ts
-const screen = render(TableBody, props)
+const screen = await render(TableBody, props)
 
 await screen.getByRole('link', { name: 'Expand' }).click()
 ```
@@ -104,7 +115,7 @@ If you find yourself using `container` to query for rendered elements then you s
 The mounted Svelte component instance. You can use this to access component methods and properties if needed.
 
 ```ts
-const { component } = render(Counter, {
+const { component } = await render(Counter, {
   initialCount: 0,
 })
 
@@ -118,7 +129,7 @@ The [locator](/api/browser/locators) of your `container`. It is useful to use qu
 ```ts
 import { render } from 'vitest-browser-svelte'
 
-const { locator } = render(NumberDisplay, {
+const { locator } = await render(NumberDisplay, {
   number: 2,
 })
 
@@ -139,15 +150,15 @@ This method is a shortcut for `console.log(prettyDOM(baseElement))`. It will pri
 #### rerender
 
 ```ts
-function rerender(props: Partial<ComponentProps<T>>): void
+function rerender(props: Partial<ComponentProps<T>>): Promise<void>
 ```
 
-Updates the component's props and waits for Svelte to apply the changes. Use this to test how your component responds to prop changes.
+Updates the component's props and waits for Svelte to apply the changes. Use this to test how your component responds to prop changes. Also records a `svelte.rerender` trace mark in the [Trace View](/guide/browser/trace-view).
 
 ```ts
 import { render } from 'vitest-browser-svelte'
 
-const { rerender } = render(NumberDisplay, {
+const { rerender } = await render(NumberDisplay, {
   number: 1,
 })
 
@@ -158,16 +169,20 @@ await rerender({ number: 2 })
 #### unmount
 
 ```ts
-function unmount(): void
+function unmount(): Promise<void>
 ```
 
-Unmount and destroy the Svelte component. This is useful for testing what happens when your component is removed from the page (like testing that you don't leave event handlers hanging around causing memory leaks).
+Unmount and destroy the Svelte component. Also records a `svelte.unmount` trace mark in the [Trace View](/guide/browser/trace-view). This is useful for testing what happens when your component is removed from the page (like testing that you don't leave event handlers hanging around causing memory leaks).
+
+::: warning
+Synchronous usage of `unmount` is deprecated and will be removed in the next major version. Please always `await` the result.
+:::
 
 ```ts
 import { render } from 'vitest-browser-svelte'
 
-const { container, unmount } = render(Component)
-unmount()
+const { container, unmount } = await render(Component)
+await unmount()
 // your component has been unmounted and now: container.innerHTML === ''
 ```
 
@@ -193,7 +208,7 @@ locators.extend({
   },
 })
 
-const screen = render(Component)
+const screen = await render(Component)
 await expect.element(
   screen.getByArticleTitle('Hello World')
 ).toBeVisible()
@@ -211,7 +226,7 @@ import { expect, test } from 'vitest'
 import SubjectTest from './basic-snippet.test.svelte'
 
 test('basic snippet', async () => {
-  const screen = render(SubjectTest)
+  const screen = await render(SubjectTest)
 
   const heading = screen.getByRole('heading')
   const child = heading.getByTestId('child')
@@ -250,7 +265,7 @@ import { expect, test } from 'vitest'
 import Subject from './complex-snippet.svelte'
 
 test('renders greeting in message snippet', async () => {
-  const screen = render(Subject, {
+  const screen = await render(Subject, {
     name: 'Alice',
     message: createRawSnippet(greeting => ({
       render: () => `<span data-testid="message">${greeting()}</span>`,

docs/api/browser/vue.md

@@ -12,7 +12,7 @@ import { expect, test } from 'vitest'
 import Component from './Component.vue'
 
 test('counter button increments the count', async () => {
-  const screen = render(Component, {
+  const screen = await render(Component, {
     props: {
       initialCount: 1,
     }
@@ -40,9 +40,20 @@ The package exposes two entry points: `vitest-browser-vue` and `vitest-browser-v
 export function render(
   component: Component,
   options?: ComponentRenderOptions,
-): RenderResult
+): RenderResult & PromiseLike<RenderResult>
 ```
 
+The `render` function records a `vue.render` trace mark, visible in the [Trace View](/guide/browser/trace-view).
+
+::: warning
+Synchronous usage of `render` is deprecated and will be removed in the next major version. Please always `await` the result:
+
+```ts
+const screen = render(Component) // [!code --]
+const screen = await render(Component) // [!code ++]
+```
+:::
+
 ### Options
 
 The `render` function supports all [`mount` options](https://test-utils.vuejs.org/api/#mount) from `@vue/test-utils` (except `attachTo` - use `container` instead). In addition to them, there are also `container` and `baseElement`.
@@ -56,7 +67,7 @@ For example, if you are unit testing a `tbody` element, it cannot be a child of
 ```js
 const table = document.createElement('table')
 
-const { container } = render(TableBody, {
+const { container } = await render(TableBody, {
   props,
   // ⚠️ appending the element to `body` manually before rendering
   container: document.body.appendChild(table),
@@ -72,7 +83,7 @@ If the `container` is specified, then this defaults to that, otherwise this defa
 In addition to documented return value, the `render` function also returns all available [locators](/api/browser/locators) relative to the [`baseElement`](#baseelement), including [custom ones](/api/browser/locators#custom-locators).
 
 ```ts
-const screen = render(TableBody, { props })
+const screen = await render(TableBody, { props })
 
 await screen.getByRole('link', { name: 'Expand' }).click()
 ```
@@ -102,7 +113,7 @@ The [locator](/api/browser/locators) of your `container`. It is useful to use qu
 ```js
 import { render } from 'vitest-browser-vue'
 
-const { locator } = render(NumberDisplay, {
+const { locator } = await render(NumberDisplay, {
   props: { number: 2 }
 })
 
@@ -125,27 +136,37 @@ This method is a shortcut for `console.log(prettyDOM(baseElement))`. It will pri
 #### rerender
 
 ```ts
-function rerender(props: Partial<Props>): void
+function rerender(props: Partial<Props>): void & PromiseLike<void>
 ```
 
+Also records a `vue.rerender` trace mark in the [Trace View](/guide/browser/trace-view).
+
 It is better if you test the component that's doing the prop updating to ensure that the props are being updated correctly to avoid relying on implementation details in your tests. That said, if you'd prefer to update the props of a rendered component in your test, this function can be used to update props of the rendered component.
 
+::: warning
+Synchronous usage of `rerender` is deprecated and will be removed in the next major version. Please always `await` the result.
+:::
+
 ```js
 import { render } from 'vitest-browser-vue'
 
-const { rerender } = render(NumberDisplay, { props: { number: 1 } })
+const { rerender } = await render(NumberDisplay, { props: { number: 1 } })
 
 // re-render the same component with different props
-rerender({ number: 2 })
+await rerender({ number: 2 })
 ```
 
 #### unmount
 
 ```ts
-function unmount(): void
+function unmount(): void & PromiseLike<void>
 ```
 
-This will cause the rendered component to be unmounted. This is useful for testing what happens when your component is removed from the page (like testing that you don't leave event handlers hanging around causing memory leaks).
+This will cause the rendered component to be unmounted. Also records a `vue.unmount` trace mark in the [Trace View](/guide/browser/trace-view). This is useful for testing what happens when your component is removed from the page (like testing that you don't leave event handlers hanging around causing memory leaks).
+
+::: warning
+Synchronous usage of `unmount` is deprecated and will be removed in the next major version. Please always `await` the result.
+:::
 
 #### emitted
 
@@ -182,7 +203,7 @@ locators.extend({
   },
 })
 
-const screen = render(Component)
+const screen = await render(Component)
 await expect.element(
   screen.getByArticleTitle('Hello World')
 ).toBeVisible()

docs/config/reporters.md

@@ -42,6 +42,7 @@ Note that the [coverage](/guide/coverage) feature uses a different [`coverage.re
 - [`tap-flat`](/guide/reporters#tap-flat-reporter)
 - [`hanging-process`](/guide/reporters#hanging-process-reporter)
 - [`github-actions`](/guide/reporters#github-actions-reporter)
+- [`agent`](/guide/reporters#agent-reporter)
 - [`blob`](/guide/reporters#blob-reporter)
 
 ## Example

docs/guide/browser/visual-regression-testing.md

@@ -606,7 +606,6 @@ screenshots should use the service.
 
 The cleanest approach is using [Test Projects](/guide/projects):
 
-
 ```ts [vitest.config.ts]
 import { env } from 'node:process'
 import { defineConfig } from 'vitest/config'
@@ -663,7 +662,6 @@ export default defineConfig({
 })
 ```
 
-
 Follow the [official guide to create a Playwright Workspace](https://learn.microsoft.com/en-us/azure/app-testing/playwright-workspaces/quickstart-run-end-to-end-tests?tabs=playwrightcli&pivots=playwright-test-runner#create-a-workspace).
 
 Once your workspace is created, configure Vitest to use it:

docs/guide/cli-generated.md

@@ -102,7 +102,7 @@ Hide logs for skipped tests
 - **CLI:** `--reporter <name>`
 - **Config:** [reporters](/config/reporters)
 
-Specify reporters (default, blob, verbose, dot, json, tap, tap-flat, junit, tree, hanging-process, github-actions)
+Specify reporters (default, agent, blob, verbose, dot, json, tap, tap-flat, junit, tree, hanging-process, github-actions)
 
 ### outputFile
 

docs/guide/cli.md

@@ -237,4 +237,3 @@ Merges every blob report located in the specified folder (`.vitest-reports` by d
 ```sh
 vitest --merge-reports --reporter=junit
 ```
-

docs/guide/reporters.md

@@ -98,6 +98,10 @@ This example will write separate JSON and XML reports as well as printing a verb
 
 By default (i.e. if no reporter is specified), Vitest will display summary of running tests and their status at the bottom. Once a suite passes, its status will be reported on top of the summary.
 
+::: tip
+When Vitest detects it is running inside an AI coding agent, the [`agent`](#agent-reporter) reporter is used instead to reduce output and minimize token usage. You can override this by explicitly configuring the [`reporters`](/config/reporters) option.
+:::
+
 You can disable the summary by configuring the reporter:
 
 :::code-group
@@ -637,6 +641,26 @@ export default defineConfig({
 })
 ```
 
+### Agent Reporter
+
+Outputs a minimal report optimized for AI coding assistants and LLM-based workflows. Only failed tests and their error messages are displayed. Console logs from passing tests and the summary section are suppressed to reduce token usage.
+
+This reporter is automatically enabled when no `reporters` option is configured and Vitest detects it is running inside an AI coding agent. If you configure custom reporters, you can explicitly add `agent`:
+
+:::code-group
+```bash [CLI]
+npx vitest --reporter=agent
+```
+
+```ts [vitest.config.ts]
+export default defineConfig({
+  test: {
+    reporters: ['agent']
+  },
+})
+```
+:::
+
 ### Blob Reporter
 
 Stores test results on the machine so they can be later merged using [`--merge-reports`](/guide/cli#merge-reports) command.