> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/getting-started/other-frameworks/vitest/troubleshooting.md).

# Troubleshooting Vitest

If you are experiencing issues with reporting Vitest results, please collect more information about the failure and submit a support request via our support channels.

### 1. Collecting Environment Information

Please collect the following information to help us effectively debug the problem:

* The associated dashboard Run URL
* The JUnit XML file produced by Vitest
* Your setup method and configuration files
* The exact commands used to run `vitest`, `currents convert` and `currents upload`
* Environment information (use the command below)

Use the following command to print information about your CI environment

```bash
npx envinfo --system --binaries --browsers --npmPackages --duplicates --npmGlobalPackages
```

### 2. Activate Debug Mode

Set `DEBUG=currents*` before running `currents convert` or `currents upload` to obtain detailed information about the conversion and upload process. Alternatively, pass the `--debug` flag to either command.

### 3. Common Issues

<details>

<summary>No results are uploaded</summary>

Check that Vitest actually wrote the JUnit XML file at the path passed to `currents convert --input-file`. Vitest only writes the file when the `junit` reporter is enabled and `outputFile.junit` is set — without `outputFile`, the report is printed to stdout instead.

</details>

<details>

<summary>Conversion or upload is skipped when tests fail</summary>

`vitest run` exits with a non-zero code when tests fail. In CI this stops the job before the results are reported. Make the conversion and upload steps run regardless of the test outcome — see [Vitest - GitHub Actions](/getting-started/other-frameworks/vitest/ci-setup/vitest-github-actions.md).

</details>

For more details on how to troubleshoot Vitest tests, refer to [their documentation](https://vitest.dev/guide/debugging).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.currents.dev/getting-started/other-frameworks/vitest/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.