@testream/go-reporter
v1.0.1
Published
Run Go tests, publish CTRF results, and send source evidence and CI metadata to Testream and Jira.
Maintainers
Readme
@testream/go-reporter: Go test reporting for Jira
@testream/go-reporter runs Go tests and publishes the results to Testream as
durable, Jira-visible evidence. Your Go test suite remains the execution source;
Testream adds failure inspection, CI context, and run history without requiring
duplicate manual cases.
What the reporter sends to Testream and Jira
- Passed, failed, skipped, and pending Go test results
- Failure status, duration, and suite structure
- Source snippets and test locations when available
- Branch, commit, build, environment, and CI metadata
- Test-run history for Jira and release reviews
Install and run in CI
- uses: actions/setup-go@v5
with:
go-version: '1.24'
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm install -g @testream/go-reporter
- run: |
testream-go \
--api-key "${{ secrets.TESTREAM_API_KEY }}" \
--fail-on-errorStore TESTREAM_API_KEY as a protected CI secret. The command works in GitHub
Actions, GitLab CI/CD, Azure Pipelines, Jenkins, and other command-based CI
systems.
Go evidence in CI/CD
The reporter publishes structured Go test results while your existing Go project and CI workflow remain unchanged. Testream connects test failures and run context to the delivery work teams already manage in Jira.
Go test failures remain CI failures after the report is published. Upload
failures are non-fatal by default; use --fail-on-error when an upload failure
should also fail the command.
Frequently asked questions
Do we need to recreate automated tests as manual Jira cases?
No. Your Go test suite remains the code-first execution source. Testream publishes its results for Jira users without requiring a duplicate manual case for every automated test.
Does the reporter replace the Go test runner?
No. It runs with your existing Go tests and adds Testream reporting around the results they produce.
