Unit Tests should only test on net462 and net8
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.5k
- Forks
- 1.4k
- Avg merge
- 9h 17m
- Merged PRs (30d)
- 24
Description
Instead of spending a lot of energy (both in maintaining build-scripts and build-server-time) on unit-testing on various platforms (NET35 + NET45 + NET46 + NET8), then instead just test with (NET462 + NET8).
Instead trust that if it compiles then it works on NET35 + NET45, since legacy platforms.
This will open the door for changing to xUnit v3, or maybe just use MsTest/VsTest ?
Contributor 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.
Research direction
Start by locating the unit-test projects and build scripts that define the NET35, NET45, NET46, and NET8 test targets. Compare how those targets are built and run, then confirm that tests run only on NET462 and NET8 while the legacy targets remain covered by compilation; the issue also leaves the xUnit v3 versus MsTest/VsTest choice open.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100