TestSuite
The TestSuite class represents a single suite. This class is only available in the main thread. Refer to the "Runner API" 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:
if (task.type === 'suite') {
task // TestSuite
}WARNING
We are planning to introduce a new Reporter API that will be using this API by default. For now, the Reporter API uses runner tasks, but you can still access TestSuite via vitest.state.getReportedEntity method:
import type { RunnerTestFile, TestModule, Vitest } from 'vitest/node'
class Reporter {
private vitest!: Vitest
onInit(vitest: Vitest) {
this.vitest = vitest
}
onFinished(files: RunnerTestFile[]) {
for (const file of files) {
const testModule = this.vitest.state.getReportedEntity(file) as TestModule
for (const suite of testModule.children.allSuites()) {
console.log(suite) // TestSuite
}
}
}
}project
This references the TestProject that the test belongs to.
module
This is a direct reference to the TestModule where the test is defined.
name
This is a suite name that was passed to the describe function.
import { describe } from 'vitest'
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":
import { describe, test } from 'vitest'
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 name, module ID and suite order.
The ID looks like this:
1223128da3_0_0_0
^^^^^^^^^^ the file hash
^ suite index
^ nested suite index
^ test indexTIP
You can generate file hash with generateFileHash function from vitest/node which is available since Vitest 3:
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 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 }:
import { describe } from 'vitest'
describe('the validation works correctly', () => {
// ...
})parent
Parent suite. If the suite was called directly inside the module, the parent will be the module itself.
options
interface TaskOptions {
each: boolean | undefined
concurrent: boolean | undefined
shuffle: boolean | undefined
retry: number | undefined
repeats: number | undefined
mode: 'run' | 'only' | 'skip' | 'todo'
}The options that suite was collected with.
children
This is a collection of all suites and tests inside the current suite.
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.
ok
function ok(): booleanChecks if the suite has any failed tests. This will also return false if suite failed during collection. In that case, check the errors() for thrown errors.
skipped
function skipped(): booleanChecks if the suite was skipped during collection.
errors
function errors(): TestError[]Errors that happened outside of the test run during collection, like syntax errors.
import { describe } from 'vitest'
describe('collection failed', () => {
throw new Error('a custom error')
})WARNING
Note that errors are serialized into simple object: instanceof Error will always return false.