@vitest-agent/mcp 1.1.0 → 1.3.0

package/vendor/vitest-docs/api/advanced/test-suite.md

@@ -1,230 +0,0 @@
-# TestSuite
-
-The `TestSuite` class represents a single suite. This class is only available in the main thread. Refer to the ["Runner API"](/api/advanced/runner#tasks) if you are working with runtime tasks.
-
-The `TestSuite` instance always has a `type` property with the value of `suite`. You can use it to distinguish between different task types:
-
-```ts
-if (task.type === 'suite') {
-  task // TestSuite
-}
-```
-
-## project
-
-This references the [`TestProject`](/api/advanced/test-project) that the test belongs to.
-
-## module
-
-This is a direct reference to the [`TestModule`](/api/advanced/test-module) where the test is defined.
-
-## name
-
-This is a suite name that was passed to the `describe` function.
-
-```ts
-import { describe } from 'vitest'
-
-// [!code word:'the validation logic']
-describe('the validation logic', () => {
-  // ...
-})
-```
-
-## fullName
-
-The name of the suite including all parent suites separated with `>` symbol. This suite has a full name "the validation logic > validating cities":
-
-```ts
-import { describe, test } from 'vitest'
-
-// [!code word:'the validation logic']
-// [!code word:'validating cities']
-describe('the validation logic', () => {
-  describe('validating cities', () => {
-    // ...
-  })
-})
-```
-
-## id
-
-This is suite's unique identifier. This ID is deterministic and will be the same for the same suite across multiple runs. The ID is based on the [project](/api/advanced/test-project) name, module ID and suite order.
-
-The ID looks like this:
-
-```
-1223128da3_0_0_0
-^^^^^^^^^^ the file hash
-           ^ suite index
-             ^ nested suite index
-               ^ test index
-```
-
-::: tip
-You can generate file hash with `generateFileHash` function from `vitest/node` which is available since Vitest 3:
-
-```ts
-import { generateFileHash } from 'vitest/node'
-
-const hash = generateFileHash(
-  '/file/path.js', // relative path
-  undefined, // the project name or `undefined` is not set
-)
-```
-:::
-
-::: danger
-Don't try to parse the ID. It can have a minus at the start: `-1223128da3_0_0_0`.
-:::
-
-## location
-
-The location in the module where the suite was defined. Locations are collected only if [`includeTaskLocation`](/config/includetasklocation) is enabled in the config. Note that this option is automatically enabled if `--reporter=html`, `--ui` or `--browser` flags are used.
-
-The location of this suite will be equal to `{ line: 3, column: 1 }`:
-
-```ts:line-numbers {3}
-import { describe } from 'vitest'
-
-describe('the validation works correctly', () => {
-  // ...
-})
-```
-
-## parent
-
-Parent suite. If the suite was called directly inside the [module](/api/advanced/test-module), the parent will be the module itself.
-
-## options
-
-```ts
-interface TaskOptions {
-  readonly each: boolean | undefined
-  readonly fails: boolean | undefined
-  readonly concurrent: boolean | undefined
-  readonly shuffle: boolean | undefined
-  readonly retry: number | undefined
-  readonly repeats: number | undefined
-  readonly tags: string[] | undefined
-  readonly mode: 'run' | 'only' | 'skip' | 'todo'
-}
-```
-
-The options that suite was collected with.
-
-## children
-
-This is a [collection](/api/advanced/test-collection) of all suites and tests inside the current suite.
-
-```ts
-for (const task of suite.children) {
-  if (task.type === 'test') {
-    console.log('test', task.fullName)
-  }
-  else {
-    // task is TaskSuite
-    console.log('suite', task.name)
-  }
-}
-```
-
-::: warning
-Note that `suite.children` will only iterate the first level of nesting, it won't go deeper. If you need to iterate over all tests or suites, use [`children.allTests()`](/api/advanced/test-collection#alltests) or [`children.allSuites()`](/api/advanced/test-collection#allsuites). If you need to iterate over everything, use recursive function:
-
-```ts
-function visit(collection: TestCollection) {
-  for (const task of collection) {
-    if (task.type === 'suite') {
-      // report a suite
-      visit(task.children)
-    }
-    else {
-      // report a test
-    }
-  }
-}
-```
-:::
-
-## ok
-
-```ts
-function ok(): boolean
-```
-
-Checks if the suite has any failed tests. This will also return `false` if suite failed during collection. In that case, check the [`errors()`](#errors) for thrown errors.
-
-## state
-
-```ts
-function state(): TestSuiteState
-```
-
-Checks the running state of the suite. Possible return values:
-
-- **pending**: the tests in this suite did not finish running yet.
-- **failed**: this suite has failed tests or they couldn't be collected. If [`errors()`](#errors) is not empty, it means the suite failed to collect tests.
-- **passed**: every test inside this suite has passed.
-- **skipped**: this suite was skipped during collection.
-
-::: warning
-Note that [test module](/api/advanced/test-module) also has a `state` method that returns the same values, but it can also return an additional `queued` state if the module wasn't executed yet.
-:::
-
-## errors
-
-```ts
-function errors(): TestError[]
-```
-
-Errors that happened outside of the test run during collection, like syntax errors.
-
-```ts {4}
-import { describe } from 'vitest'
-
-describe('collection failed', () => {
-  throw new Error('a custom error')
-})
-```
-
-::: warning
-Note that errors are serialized into simple objects: `instanceof Error` will always return `false`.
-:::
-
-## meta <Version>3.1.0</Version> {#meta}
-
-```ts
-function meta(): TaskMeta
-```
-
-Custom [metadata](/api/advanced/metadata) that was attached to the suite during its execution or collection. Since Vitest 4.1, the meta can be attached by providing a `meta` object during test collection:
-
-```ts {7,10}
-import { describe, test, TestRunner } from 'vitest'
-
-describe('the validation works correctly', { meta: { decorated: true } }, () => {
-  test('some test', ({ task }) => {
-    // assign "decorated" during test run, it will be available
-    // only in onTestCaseReady hook
-    task.suite.meta.decorated = false
-
-    // tests inherit suite's metadata
-    task.meta.decorated === true
-  })
-})
-```
-
-Note that suite metadata will be inherited by tests since Vitest 4.1.
-
-:::tip
-If metadata was attached during collection (outside of the `test` function), then it will be available in [`onTestModuleCollected`](./reporters#ontestmodulecollected) hook in the custom reporter.
-:::
-
-## toTestSpecification <Version>4.1.0</Version> {#totestspecification}
-
-```ts
-function toTestSpecification(): TestSpecification
-```
-
-Returns a new [test specification](/api/advanced/test-specification) that can be used to filter or run this specific test suite.