@testream/dotnet-reporter: .NET test reporting for Jira

@testream/dotnet-reporter runs .NET tests or ingests TRX, then publishes xUnit, NUnit, and MSTest results to Testream as durable evidence visible from Jira. Your C# test suite remains the execution source, with no need to recreate every automated test as a manual Jira case.

What the reporter sends to Testream and Jira

• xUnit, NUnit, and MSTest results read from TRX
• Failure messages, stack traces, duration, and suite structure
• Bounded C# method snippets when TRX source paths can be resolved
• Branch, commit, build, environment, and CI metadata, including merge-base data for pull-request comparisons
• Suite changes and trends for Jira 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.

Testream connects .NET execution to the delivery work teams already manage in Jira without replacing the existing test project or pipeline.

Install and run in CI

- uses: actions/setup-dotnet@v4
  with:
    dotnet-version: '8.0.x'

- uses: actions/setup-node@v4
  with:
    node-version: '20'

- run: npm install -g @testream/dotnet-reporter

- run: |
    testream-dotnet \
      --api-key "${{ secrets.TESTREAM_API_KEY }}" \
      --fail-on-error

This installs the reporter, runs the .NET tests, and publishes their results. When TRX metadata includes source file paths, the reporter enriches CTRF tests with bounded C# method snippets from the corresponding .cs files.

.NET evidence in CI/CD

Store TESTREAM_API_KEY as a protected secret. The command works in GitHub Actions, Azure Pipelines, GitLab CI/CD, Jenkins, and other command-based CI providers, preserving build and source context for later Jira review.

Frequently asked questions

Do we need to recreate automated tests as manual Jira cases?

No. xUnit, NUnit, or MSTest remains the code-first execution source. Testream adds Jira visibility without duplicate manual cases.

Can the reporter ingest an existing TRX file?

Yes. The reporter supports TRX produced by an existing .NET test workflow as well as running tests within its normal command flow.

Official Testream resources

• .NET Jira integration
• Complete .NET reporter setup guide
• Install Testream – Automated Test Management for Jira