Unit Tests should only test on net462 and net10
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- build-system, testing
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.
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 ?
- Dominant language
- C#
- Stars
- 6.5k
- Forks
- 1.4k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 34
Getting set up
- No Dockerfile or Docker Compose file
- No 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 NLog/NLog
-
documentation
Difficulty 2/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
discussion
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
DateLayoutRenderer default Format should be culture invariantPossibly taken @HarnageaGabriel claimed this 88 days ago. Openbreaking behavior change breaking change
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 38/100
Maintainers usually reply within 1 day
-
Move to slnxOpen
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
[中] 更新器下载缓存从不清理Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Remove duplicate Vimeo DI registration; use NimblePros.Vimeo AddVimeoServices and upgrade packageOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DevBetterCom/DevBetterWeb#1486 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NimblePros/eShopOnWeb#333 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Natvs/Nt.Automaton#33 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100