microsoft / microsoft/VFSForGit
Create constants project to share between product and test code
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
We frequently have developer headaches when we update a string literal in the product code but forget to update it in the tests. This is particularly painful when the test only runs in the full functional test suite.
Create a new project full of constants that we can use across product and test code.
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 examining how string literals are defined in the product code and duplicated in the tests, then identify the project structure used for shared C# code. Define the constants project and update both product and test references so changed values cannot drift; verify the full functional test suite still passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- developer-experience, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100