Support relative & absolute path for "--file=" #25
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, when using the
--file=
flag to run a specific test, the path for each test attest.file
was a static-path starting atAreas/**/*unittests.js
..Meaning to achieve a match, you always had to provide a path starting atAreas
, likeAreas\Studio\Tests\Commands\ChangeDesign.unittests.js
.This change causes the
--flag=
to look for unit test matches based on absolute pathing and relative pathing from the origin of grunt js-test.