Vitest

Everr automatically parses Vitest output to track test results, detect flaky tests, and analyze failures.

Supported reporters

Verbose reporter (recommended)

The verbose reporter prints every individual test result, giving Everr full per-test visibility:

vitest run --reporter=verbose

Or configure it in your vitest.config.ts:

export default defineConfig({
  test: {
    reporters: ["verbose"],
  },
});

Default reporter

The default reporter (no extra configuration needed) is also supported. Everr parses:

• File-level summaries for every test file (pass/fail status and duration)
• Individual slow tests that Vitest prints below each file summary

Since the default reporter only shows individual results for slow tests, the verbose reporter gives more granular per-test tracking.

GitHub Actions workflow example

- name: Run tests
  run: npx vitest run --reporter=verbose

Everr automatically detects and parses Vitest output from workflow logs.

What gets parsed

Verbose reporter patterns

Default reporter patterns

Describe block hierarchy

Vitest verbose output uses the > separator to represent the test hierarchy: file path, describe blocks, and test name. For example:

✓ src/utils.test.ts > parseConfig > handles empty input 3ms

This is parsed as:

• Package: src/utils.test.ts
• Describe block: parseConfig
• Test name: handles empty input

Nested describe blocks are automatically detected. Describe nodes get everr.test.is_suite=true, nested entries get everr.test.is_subtest=true, and everr.test.parent_test points to the parent node. A nested describe block can therefore be both a suite and a subtest.

Generated span attributes