Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
test: enable MapManager unit test discovery #3
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
Uh oh!
There was an error while loading. Please reload this page.
test: enable MapManager unit test discovery #3
Changes from all commits
19345b0File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this
net48project, implicit global usings are not enabled in the project file, soAppContextis not in scope here. A clean build of the test assembly will fail on this added expression before discovery can run; addusing System;or qualify it asSystem.AppContextso the new discovery setup can compile.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When this project is restored without central package versions (there is no
Directory.Packages.propsin the repo), this versionlessPackageReferencedoes not mean “latest”; NuGet restores the lowest available version for an unbounded dependency (NU1604 docs). The xUnit v3 docs requirexunit.runner.visualstudio3.0+ for v3 support (xUnit package docs), so a clean restore can select a 2.x adapter anddotnet test/Test Explorer still won't discover thexunit.v3tests. Please pin this package to>= 3.0.0(or add a central version).Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a test or helper actually uses a shared map/font/symbol file, this copies
..\MapManager\Shared\**under the test output'sSharedchild becauseCopyToOutputDirectoryrespectsLinkmetadata (MSBuild item docs). HoweverMapManager.Apis.Config.Sharedresolves shared files two parents above the assembly directory plusShared(for examplebin\Sharedfrombin\Debug\net48), so these copied files land in a directory the code never reads andSharedDefaultMap.File.Exists/file opens can still fail after build. Use aTargetPathor copy target that places them in theShareddirectory thatConfig.Sharedresolves.Useful? React with 👍 / 👎.