Fix working directory while discovering tests #29
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.
Previously the working directory used in DiscoverTests(ITestAttribute, string, Action, Action) is something like
SomeProject/bin/Debug/net5.0/SomeProject.dll
, so loading test specs from the output directory (such asSomeProject/bin/Debug/net5.0/specs/a.yml
) will fail and report a warning likeNo file is found in directory 'SomeProject/bin/Debug/net5.0/SomeProject.dll' using glob pattern 'specs/*.yml'
. In code I found thatsourcePath
is calculated as the directory containing the test DLL but never used. This simple fix will allow users to load test specs from the output directory, as it should be by design.