Previously, when using the --file= flag to run a specific test, the path for each test at test.file was a static-path starting at Areas/**/*unittests.js..Meaning to achieve a match, you always had to provide a path starting at Areas, like Areas\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.
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.