npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@testream/dotnet-reporter

v0.4.0

Published

CLI to upload .NET test results (xUnit, NUnit, MSTest) to Testream

Readme

@testream/dotnet-reporter

Run .NET tests and upload results to Testream with a single command.

Features

  • Zero Configuration - Just run and upload, no TRX path needed
  • All .NET Frameworks - Works with xUnit, NUnit, and MSTest
  • Auto-Detection - Detects test framework and git context automatically
  • CI/CD Ready - Works in GitHub Actions, GitLab CI, Azure Pipelines, and more

Quick Start

# One command does everything!
npx @testream/dotnet-reporter -p MYPROJ -k your-api-key

That's it! The CLI will:

  1. Run dotnet test
  2. Generate a test report
  3. Upload to Testream

Installation

# Use directly with npx (recommended)
npx @testream/dotnet-reporter ...

# Or install globally
npm install -g @testream/dotnet-reporter
testream-dotnet ...

Usage

Basic Usage

# Run tests in current directory and upload
npx @testream/dotnet-reporter -p MYPROJ -k $API_KEY

# Run tests for a specific project
npx @testream/dotnet-reporter -p MYPROJ -k $API_KEY --project ./MyTests

# Run tests for a solution
npx @testream/dotnet-reporter -p MYPROJ -k $API_KEY --project ./MySolution.sln

Pass Arguments to dotnet test

# Filter tests
npx @testream/dotnet-reporter -p MYPROJ -k $API_KEY -- --filter "Category=Unit"

# Set configuration
npx @testream/dotnet-reporter -p MYPROJ -k $API_KEY -- --configuration Release

# Multiple arguments
npx @testream/dotnet-reporter -p MYPROJ -k $API_KEY -- --filter "Category=Unit" --no-build

Use Existing TRX File

If you've already run tests and have TRX file(s):

npx @testream/dotnet-reporter -p MYPROJ -k $API_KEY --trx-path TestResults/*.trx

CLI Options

| Option | Description | |--------|-------------| | -p, --project-key | (Required) Jira project key | | -k, --api-key | (Required) API key for authentication | | --project <path> | Path to .NET project/solution (defaults to current directory) | | --trx-path <path> | Use existing TRX file(s) instead of running tests | | --test-tool | Test framework name (auto-detected) | | --branch | Git branch (auto-detected in CI) | | --commit-sha | Git commit SHA (auto-detected in CI) | | -- <args> | Additional arguments to pass to dotnet test |

GitHub Actions Example

name: Tests

on: [push, pull_request]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

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

      - name: Run tests and upload
        run: |
          npx @testream/dotnet-reporter \
            -p ${{ secrets.PROJECT_KEY }} \
            -k ${{ secrets.API_KEY }} \
            --project ./MySolution.sln \
            --test-tool xunit \
            --branch ${{ github.ref_name }} \
            --commit-sha ${{ github.sha }} \
            --repository-url ${{ github.server_url }}/${{ github.repository }} \
            --build-name ${{ github.workflow }} \
            --build-number ${{ github.run_number }} \
            --build-url ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }} \
            --test-environment ci \
            --app-name MyApp \
            --app-version 1.0.0 \
            --test-type unit \
            --fail-on-error \
            -- --configuration Release

How It Works

┌──────────────────────────────────────────┐
│  @testream/dotnet-reporter               │
├──────────────────────────────────────────┤
│  1. Run dotnet test                      │
│  2. Generate report                      │
│  3. Upload to Testream                   │
└──────────────────────────────────────────┘

It all happens automatically - just provide your project key and API key!

Supported Frameworks

| Framework | Version | Status | |-----------|---------|--------| | xUnit | 2.x+ | ✅ Tested | | NUnit | 4.x+ | ✅ Tested | | MSTest | 3.x+ | ✅ Tested |

Supported CI Platforms

Git context (branch, commit, repository) is auto-detected in:

  • GitHub Actions
  • GitLab CI
  • Azure Pipelines
  • CircleCI
  • Jenkins
  • Bitbucket Pipelines

License

See LICENSE file.