Idiomatic Test Organization
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
Start by reviewing pull request 476 and the repository's current source and test layout. Identify each assembly under test and its existing test project, then compare the organization against the issue's four requested patterns. Done means the test projects, namespaces, and integration-test boundaries consistently reflect those patterns.
Written by the indexing model from the issue text.
Description
The new code organization in https://github.com/microsoft/OSSGadget/pull/476 paves the way for this repository to move towards more idiomatic .NET unit tests. For example:
- source and tests in different directories
- one test project for each assembly under test (i.e.,
Shared.CLI.Testsfor theShared.CLIproject andShared.Lib.Testsfor theShared.Libproject.) - test code organization mirroring the assembly under test (e.g., Shared.CLI.Tests.Tools.DefoggerToolTests
rather thanMicrosoft.CST.OpenSource.Tests.DefoggerTests`) - isolating integration tests to a separate test assembly
- Dominant language
- C#
- Stars
- 372
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No 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 microsoft/OSSGadget
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 4/5 3-5 days Newbie friendliness 54/100
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
All issues in microsoft/OSSGadget
Similar issues
-
feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
stripe/stripe-dotnet#3484 ·
Maintainers usually reply within 2 days
-
bug mcp misleading small
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
accessibility help wanted macos
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dorlugasigal/annotator#42 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
AvaloniaUI/Avalonia#22568 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
LorisYounger/VPet#589 · 2 comments ·