Generator snapshot test builds warn that Verify cannot choose among solution files
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #7488 by @thomhurst — merged
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start with the test project file tests/TUnit.Core.SourceGenerator.Tests, where the Verify solution properties would be set. Reproduce by running dotnet test on that project and confirm the warning about TUnit.CI.slnx, TUnit.Dev.slnx and TUnit.slnx appears. Done when the build no longer emits the Verify solution-discovery warning and the snapshot tests still pass.
Written by the indexing model from the issue text.
Description
Summary
Building the core source generator snapshot tests emits a Verify warning because it discovers three solution files and cannot choose a solution directory or name. Configure these properties explicitly so routine test builds do not emit this warning.
Reproduction
At ca4437c718, with .NET SDK 10.0.403 on macOS arm64, run:
dotnet test --project tests/TUnit.Core.SourceGenerator.Tests --framework net10.0
Expected and actual
Expected: Verify can identify the solution context without warnings.
Actual: Verify 33.3.4's buildTransitive/Verify.props reports that TUnit.CI.slnx, TUnit.Dev.slnx and TUnit.slnx make solution discovery ambiguous. It recommends setting SolutionDir and SolutionName explicitly.
Please configure the test build's Verify solution context.
- Dominant language
- C#
- Stars
- 4k
- Forks
- 139
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 325
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- 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 thomhurst/TUnit
-
documentation P3
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
thomhurst/TUnit#7444 · 1 comment ·
Maintainers usually reply within 1 day
-
Mock and core generator test restores report vulnerable System.Security.Cryptography.Pkcs versionsOpendependencies P2
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
thomhurst/TUnit#7412 · 8 comments ·
Maintainers usually reply within 1 day
-
enhancement P3 performance
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
thomhurst/TUnit#7380 · 2 comments ·
Maintainers usually reply within 1 day
-
bug github_actions P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
thomhurst/TUnit#7229 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement P3
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
thomhurst/TUnit#7194 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
needs-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
bug github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
endercodezz/BYDLO#336 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
SubtitleEdit/subtitleedit#16638 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
sebastienros/jint#4449 ·
Maintainers usually reply within 1 day