vitest-5-0-0-9-b

Question

Which folder does vitest --merge-reports read from by default?

Answer key

A correct answer says

The blob reporter and --merge-reports use .vitest/blob/ by default.

The stale answer

Blob reports go to .vitest-reports/ by default.

The change's lesson

Answer

By default, `vitest --merge-reports` reads from the **`.vitest-reports`** folder in the project root. The `blob` reporter also writes there by default, as `.vitest-reports/blob-<shard>-<total>.json` per run or shard. That means you can run sharded tests with `--reporter=blob` and then run `vitest --merge-reports` without extra flags. To read from a different folder, give it as the flag's value, e.g. `vitest --merge-reports=./my-reports`. If you changed the blob reporter's `outputFile`, the folder you pass should match it.

Answering cost $0.05.

Grade

wrong

The judge's reason: It says the default folder is .vitest-reports/, which is the stale behavior, not the current .vitest/blob/.

The judge's log

Session log

What the agent wrote, the tools it called, and what they returned, from docs/bench/2026-10-11-done3/runs/B-project/vitest-5-0-0-9-b.jsonl. Thinking and the session's settings are left out. The raw log

1. Agent

   By default, `vitest --merge-reports` reads from the **`.vitest-reports`** folder in the project root. The `blob` reporter also writes there by default, as `.vitest-reports/blob-<shard>-<total>.json` per run or shard. That means you can run sharded tests with `--reporter=blob` and then run `vitest --merge-reports` without extra flags. To read from a different folder, give it as the flag's value, e.g. `vitest --merge-reports=./my-reports`. If you changed the blob reporter's `outputFile`, the folder you pass should match it.