linksplatform / linksplatform/Data.Doublets
Give structure to the Tests folder.
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 14
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Reason: Ease of maintenance especially when code grow bigger.
Example:
Data.Doublets:
Subdirectory:
Program.cs
Data.Doublets.Tests:
Subdirectory:
ProgramTest1.cs
ProgramTest2.cs
ProgramTest3.cs
Instead of
Data.Doublets:
Subdirectory:
Program.cs
Data.Doublets.Tests:
ProgramTest1.cs
ProgramTest2.cs
ProgramTest3.cs
I have found some repositories that use this "method":
Contributor guide
No contributing guide indexed for this repository
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
Inspect the Tests folder and compare its layout with the production subdirectories described in the issue, using the Program.cs and ProgramTest1.cs–ProgramTest3.cs examples as the intended pattern. Confirm which test files correspond to each source subdirectory, reorganize them consistently, and run the existing test suite to verify everything still passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100