`rtk dotnet test` counts a project once per output line that names its `.csproj`
Maintainers usually reply within 1 day
@ecoyoung is already working on this.
Since Oct 30, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start by reading binlog::parse_test_from_text and count_projects, then check the existing tests for rtk dotnet test output parsing. Reproduce with warning lines that repeat each .csproj path and compare the reported count with the two projects that ran. Done means the summary counts each project once for plain output and with --logger trx.
Written by the indexing model from the issue text.
Description
rtk dotnet test reports one project per output line that names a .csproj, so warnings inflate the in N projects count.
Measured with the .NET 10.0.400 SDK on a solution with two xunit test projects, develop 7e92da00a:
| command | native | rtk dotnet … |
|---|---|---|
test -v q --filter 'FullyQualifiedName~Tests2.', restore printing 4 warning NU1900 lines (two per project) |
2 test projects run (A total of 1 test files matched twice) |
fail dotnet test: 1 passed, 1 failed, 0 skipped, 4 warnings in 4 projects |
binlog::parse_test_from_text sets project_count: count_projects(&scrubbed).max(1), and count_projects counts every PROJECT_PATH_RE match in the whole output. Each warning line names its project, so a project named in two warning lines is counted twice. The TRX-derived count (2 here) only replaces it when larger (trx_summary.project_count > summary.project_count), so the console count wins. Reproduced on develop with plain rtk dotnet test and with --logger trx; that line of parse_test_from_text has been there since v0.34.2.
A fix would count distinct projects, for example from the Test run for <dll> or Failed!/Passed! … - <dll> lines, rather than path matches.
- Dominant language
- Rust
- Stars
- 85k
- Forks
- 5.4k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 58
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rtk-ai/rtk
-
rtk git show <commit>: truncation hint points to `rtk git diff --no-compact`, which does not show the commitPossibly taken @vshalpnjabi claimed this 1 day ago. Openarea:cli bug good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
rtk-ai/rtk#4817 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Windows: .hook_warn_last mtime never advances, so the daily hook reminder prints on every commandPossibly taken @ShryukGrandhi claimed this 5 days ago. Openarea:cli bug good first issue platform:windows priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
rtk-ai/rtk#4746 · 2 comments ·
Maintainers usually reply within 1 day
-
test: help_passthrough_fuzz_test opens git's HTML manual pages in the browser on WindowsPossibly taken @viniciusdsandrade claimed this 5 days ago. Openarea:testing bug good first issue platform:windows priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
`rtk ruff check --statistics` prints ruff's statistics JSON instead of its table, larger than ruff's own outputPossibly taken @umi008 claimed this 8 days ago. Openarea:cli bug good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
rtk jira: filtered output keeps trailing line padding — 30-39% of the result is spaces (v1.0.1)Possibly taken @umi008 claimed this 8 days ago. Openarea:cli bug good first issue priority:low
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
compiler P4 perf
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
HerringtonDarkholme/hd-lang#1044 ·
Maintainers usually reply within 1 day
-
good first issue help wanted r-docs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
servo/rust-smallvec#824 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
akitaonrails/ai-usagebar#552 ·
Maintainers usually reply within 1 day