Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test dotnet resolution algorithm #4132

Closed
cvpoienaru opened this issue Nov 22, 2022 · 1 comment · Fixed by #4210
Closed

Test dotnet resolution algorithm #4132

cvpoienaru opened this issue Nov 22, 2022 · 1 comment · Fixed by #4210
Assignees

Comments

@cvpoienaru
Copy link
Member

This issue is related to the following change: #4122.

Tests were already written to make sure the new behavior is correctly taken into account, however some essential coverage is missing. We should also test the resolution algorithm when the environment is fully set up to follow the mechanism to the end, but only one resolution strategy at a time is specified, drawn from the following list:

  • DotnetMuxerResolutionStrategy.DotnetRootArchitecture
  • DotnetMuxerResolutionStrategy.DotnetRootArchitectureLess
  • DotnetMuxerResolutionStrategy.GlobalInstallationLocation
  • DotnetMuxerResolutionStrategy.DefaultInstallationLocation

Sketch data rows for the test:
[Inline(DotnetMuxerResolutionStrategy...), expected return, expected muxer]
[Inline(DotnetMuxerResolutionStrategy...), expected return, expected muxer]
[Inline(DotnetMuxerResolutionStrategy...), expected return, expected muxer]
[Inline(DotnetMuxerResolutionStrategy...), expected return, expected muxer]

@cvpoienaru
Copy link
Member Author

@MarcoRossignoli, assigning this to you as per our offline discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants