microsoft / microsoft/VFSForGit
Improve test coverage around symlinks
Open
Nobody has claimed this yet.
affects: tests
platform: linux
platform: macOS
platform: windows
pri2
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
Recent issues (#1478, #1479) that were not caught by our tests highlight that we have room to improve our coverage around symlink scenarios.
Add tests that would have helped detect bugs where VFS4G and PrjFS were incorrectly following links when they should not.
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
Review issues #1478 and #1479 first to identify the symlink scenarios that were missed. Then inspect the existing VFS4G and PrjFS test coverage and add regression tests for links that must not be followed. Done means the tests detect both reported classes of incorrect link-following behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- operating-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100