Visual Studio verification integration tests should not implicitly discover their tool chain
Open
debt
- Dominant language
- No language data
- Stars
- 94
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Like https://github.com/gradle/gradle-native/issues/393, our msbuild based VS generation tests should use the tool chain we expect them to use and not the tool chain they implicitly discover.
Contributor guide
Research direction
Start by reading the related issue gradle-native#393, then locate the msbuild-based Visual Studio generation integration tests mentioned here. Identify how those tests currently discover their tool chain; done means they consistently use the expected tool chain instead of an implicitly discovered one.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100