Repository navigation
ci-unit-tests: publish test results and coverage through the test runner and ReportGenerator - #48
Merged
Merged
Conversation
…enerator Test results: the HTML logger beside the TRX, and the excluded tests as vstest lists them by category, uploaded together. Coverage: ReportGenerator merges the per-project reports, keeps only files in the checkout outside .ci, and produces the Html report; the headline is read from its JsonSummary. The summary is #45's table plus one coverage line and links. Removed: the solution comparison diagnostic, the coverage PR comment and its pr_number input. upload-artifact moves to v7.0.2.
…om nothing to measure
sakanni
marked this pull request as ready for review
November 3, 2026 13:05
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issues addressed by this PR
Closes #47
Hands the reporting in
ci-unit-teststo the tools that already run. Discovery, the test run, the verdicts, the per-project table and the annotations from #45 are unchanged.dotnet vstestlists the tests excluded byRequiresExternalSoftware, one file per project. The TRX, HTML and excluded listings are uploaded as one artifact..ci, and produces its HTML report, uploaded as an artifact. The job summary gets one coverage line read from ReportGenerator's JSON summary, and links to whichever artifacts were uploaded.pr_numberinput, and the diagnostic comparing discovery with the old solution-driven selection.actions/upload-artifactmoves to v7.0.2, pinned by SHA. Every reporting step iscontinue-on-error, so none can change the check's outcome.Test files
Not applicable. Run side by side with the action on
developagainst purpose-built probe projects (all excluded, build failure, every project failing to build, empty project, failing test, inconclusive, parameterised, net48 without coverage, duplicate method names across fixtures, generic fixtures, custom test names), a single-project toolkit with 714 tests, and BHoM_Engine. The per-project tables, the test step's outcome and the error annotations were identical in every case; the only difference is the removed diagnostic's notices.action.ymlis 492 lines, against 510 ondevelop.Changelog
ci-unit-testspublishes test results as TRX and HTML with per-project lists of excluded testsci-unit-testspublishes ReportGenerator's HTML coverage report as an artifact instead of a markdown table and pull-request commentci-unit-testsno longer takes apr_numberinputAdditional comments
One inaccuracy is accepted. When ReportGenerator merges reports from several test projects, a partial class with two files of the same name in different folders gains the other file's lines. On BHoM_Engine that adds 104 uncovered lines to Serialiser_Engine, which shows 39.2% instead of 41.4%; the repository headline reads 7.1% either way. Single-project repositories are unaffected. This is a ReportGenerator limitation, not something the action introduces.