Analysis updated 2026-07-11 · repo last pushed 2021-01-11
Run .NET tests on pull requests and display pass/fail badges in your README.
Generate separate test reports for different test suites like business logic and service layers.
Configure pull request checks to automatically fail when tests fail to catch regressions.
Publish test result badges to a GitHub Gist for a live test health indicator.
| kayone/dotnet-tests-report | 0xhassaan/nn-from-scratch | 0xzgbot/hermes-comfyui-skills | |
|---|---|---|---|
| Stars | — | 0 | 0 |
| Language | — | Python | — |
| Last pushed | 2021-01-11 | — | — |
| Maintenance | Dormant | — | — |
| Setup difficulty | easy | moderate | easy |
| Complexity | 2/5 | 4/5 | 1/5 |
| Audience | developer | developer | designer |
Figures from each repo's GitHub metadata at analysis time.
Requires a GitHub access token and pointing the action to your test project folder.
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.
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.
Dormant — no commits in 2+ years (last push 2021-01-11).
The explanation does not specify a license, so the licensing terms for this repository are unknown.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.