explaingit

kayone/dotnet-tests-report

Analysis updated 2026-07-11 · repo last pushed 2021-01-11

Audience · developerComplexity · 2/5DormantSetup · easy

TLDR

A GitHub Action that runs your .NET tests and generates readable reports with pass/fail badges directly on your workflow runs and optionally in GitHub Gists.

Mindmap

mindmap
  root((repo))
    What it does
      Runs NET tests
      Generates reports
      Creates badges
    Tech stack
      PowerShell
      GitHub Actions
      NET testing
    Use cases
      CI test visibility
      Block PRs on failure
      Multiple test suites
    Audience
      NET developers
      DevOps teams
    Setup
      Needs GitHub token
      Point to test folder
      Opt in to fail PRs
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Run .NET tests on pull requests and display pass/fail badges in your README.

USE CASE 2

Generate separate test reports for different test suites like business logic and service layers.

USE CASE 3

Configure pull request checks to automatically fail when tests fail to catch regressions.

USE CASE 4

Publish test result badges to a GitHub Gist for a live test health indicator.

What is it built with?

PowerShellGitHub Actions.NETxUnitNUnitMSTest

How does it compare?

kayone/dotnet-tests-report0xhassaan/nn-from-scratch0xzgbot/hermes-comfyui-skills
Stars00
LanguagePython
Last pushed2021-01-11
MaintenanceDormant
Setup difficultyeasymoderateeasy
Complexity2/54/51/5
Audiencedeveloperdeveloperdesigner

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Requires a GitHub access token and pointing the action to your test project folder.

The explanation does not specify a license, so the licensing terms for this repository are unknown.

In plain English

dotnet-tests-report is a GitHub Action that runs your .NET test suites automatically and then produces readable reports and badges you can share. Instead of digging through raw log output to figure out whether your tests passed, you get a clean summary attached directly to your GitHub workflow run, plus optional badges you can display in your repository or README. At a high level, you point the action at a test project folder, give the report a name and title, and provide your GitHub access token. The action runs your tests using popular .NET testing frameworks like xUnit, NUnit, or MSTest, collects the results, and generates a report that shows up as a check run on your workflow. You can also configure it to publish a report to a GitHub Gist and create a badge that displays something like "47/50 passed," giving you a live, at-a-glance indicator of test health. This is useful for any team building .NET projects on GitHub that wants continuous visibility into test results without manually inspecting logs. For example, if you maintain separate test suites for a business logic layer and a service layer, you can run each through the action and get distinct reports and badges for both. You can also configure the check to fail pull requests automatically when tests fail, which helps catch regressions before they get merged. One notable detail is that the action is built as a PowerShell GitHub Action, which is a less common implementation choice. By default, the check status it reports is set to "neutral" rather than pass or fail, so teams need to explicitly opt in if they want test failures to block pull requests. The README doesn't go into much detail beyond configuration and samples, so further customization would require looking at the action's source.

Copy-paste prompts

Prompt 1
Help me write a GitHub Actions workflow YAML that uses the kayone/dotnet-tests-report action to run my xUnit tests and post a badge to my README.
Prompt 2
Show me how to configure the dotnet-tests-report action so that my pull request fails automatically when .NET tests fail instead of reporting a neutral status.
Prompt 3
I have separate test projects for my business logic and service layers. Write two dotnet-tests-report job steps that generate distinct reports and badges for each.
Prompt 4
Generate a GitHub Actions workflow that uses dotnet-tests-report to run MSTest and publish the results badge to a GitHub Gist.

Frequently asked questions

What is dotnet-tests-report?

A GitHub Action that runs your .NET tests and generates readable reports with pass/fail badges directly on your workflow runs and optionally in GitHub Gists.

Is dotnet-tests-report actively maintained?

Dormant — no commits in 2+ years (last push 2021-01-11).

What license does dotnet-tests-report use?

The explanation does not specify a license, so the licensing terms for this repository are unknown.

How hard is dotnet-tests-report to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is dotnet-tests-report for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.