Custom reporters can't access per-attempt details for retries

Clear and concise description of the problem

Custom reporters receive a single TestCase result per test, even when the test ran multiple times via retry. There's no way to access the individual attempts — their status, duration, errors, annotations, or stdio.

Repro: a test with retry: 3 that fails twice then passes — the reporter only sees one result with state: 'passed'.

Alternative

No response

Additional context

This was discovered while building @flakiness/vitest
For reference, Playwright Test exposes this in its reporter API: each retry comes through as a separate TestResult with its own status, duration, errors, attachments, and stdio.

Validations

Follow our Code of Conduct
Read the Contributing Guidelines.
Read the docs.
Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.

There's no way to access the individual attempts — their status, duration, errors, annotations, or stdio.

Errors are present in errors:

vitest/packages/vitest/src/node/reporters/reported-tasks.ts

Lines 635 to 640 in ab09822

    
             /** 
        
              * Errors that were thrown during the test execution. 
        
              * 
        
              * **Note**: If test was retried successfully, errors will still be reported. 
        
              */ 
        
             readonly errors: ReadonlyArray<TestError> | undefined

But I don't think other metrics are stored.

the reporter only sees one result with state: 'passed'.

From diagnostic().retryCount you can see how many times test was retried. So it kind of indicates there were 2x state: 'failed' before the last result.

From diagnostic().retryCount you can see how many times test was retried. So it kind of indicates there were 2x state: 'failed' before the last result.

Indeed, that's precisely what we do:

https://github.com/flakiness/vitest/blob/c67b1196918a1aed10df1145b6c710732bd48f67/src/reporter.ts#L259-L282

Errors are present in errors:

While they are stored there, it's hard to assign them to individual attempts since each attempt might have more than one error.

A contrived example:

import { expect, it } from 'vitest';

it('fate', async () => {
  expect.soft(0.5).toBeLessThan(Math.random());
  expect.soft(0.5).toBeGreaterThan(Math.random());
});

I like attempts concept, it could be defined on task.result, I think. It should also probably include repeats runs though.

Navigation Menu

Repository navigation

Custom reporters can't access per-attempt details for retries #10303

Clear and concise description of the problem

Suggested solution

Alternative

Additional context

Validations

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	/**
	* Errors that were thrown during the test execution.
	*
	* Note: If test was retried successfully, errors will still be reported.
	*/
	readonly errors: ReadonlyArray<TestError> \| undefined

Custom reporters can't access per-attempt details for retries #10303

Description

Clear and concise description of the problem

Suggested solution

Alternative

Additional context

Validations

Activity

AriPerkkio commented on May 9, 2026

aslushnikov commented on May 9, 2026

sheremet-va commented on May 10, 2026

puneetdixit200 commented on May 16, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions