@testream/vitest-reporter
v1.2.7
Published
Publish Vitest test results, failures, source locations, and CI metadata to Testream and Jira.
Downloads
535
Maintainers
Readme
@testream/vitest-reporter: Vitest test reporting for Jira
@testream/vitest-reporter publishes fast Vitest unit and frontend test results from CI/CD to Testream as durable, Jira-visible evidence. Vitest remains the execution source, so teams do not need to recreate every automated test as a manual Jira case.
What the reporter sends to Testream and Jira
- Passed, failed, skipped, and pending Vitest results
- Failure messages, stack traces, source locations, and bounded snippets
- Branch, commit, build, environment, and CI metadata, including merge-base data for pull-request comparisons
- Suite changes and trends for Jira work and release reviews
For pull requests, the reporter uses an explicit TESTREAM_MERGE_BASE_SHA or provider-supplied merge-base metadata; otherwise it resolves git merge-base from the existing checkout without fetching. Keep history available (fetch-depth: 0 on GitHub Actions); if no merge base can be resolved, Testream falls back to execution-time comparison.
It fits Vite-based React, Vue, Angular, and other JavaScript or TypeScript projects that need automated test reporting connected to Jira.
Install and configure
npm install --save-dev @testream/vitest-reporter// vitest.config.ts
import { defineConfig } from 'vitest/config'
export default defineConfig({
test: {
reporters: [
'default',
['@testream/vitest-reporter', {
apiKey: process.env.TESTREAM_API_KEY,
uploadEnabled: true,
}],
],
},
})The reporter enables Vitest includeTaskLocation automatically so generated CTRF reports include line metadata and shared snippet enrichment can populate source evidence for JavaScript and TypeScript tests.
Vitest evidence in CI/CD
Keep your normal Vitest command and store TESTREAM_API_KEY as a protected secret. The reporter publishes the completed run from GitHub Actions, GitLab CI/CD, Azure Pipelines, Jenkins, or another command-based CI provider. Testream then connects the results to Jira work and release context.
Frequently asked questions
Do we need to recreate automated tests as manual Jira cases?
No. Your Vitest suite remains the code-first execution source. Testream makes the results inspectable in Jira without introducing duplicate manual cases.
Does it work outside React projects?
Yes. The reporter works with Vitest itself, including Vue, Angular, Vite, and other projects that use Vitest for unit or frontend testing.
