tools/test.py should be able to get a full path to a test to manually run it

[MylesBorins]

Currently if you want to manually run a test you have to remove test/ from the beginning of the path and not include the js prefix.

For example the following commands will not work

$ python tools/test.py test/parallel/test-cluster-worker-init.js
$ python tools/test.py test/parallel/test-cluster-worker-init
$ python tools/test.py parallel/test-cluster-worker-init.js

but the following will

$ python tools/test.py parallel/test-cluster-worker-init

I find this counter intuitive and would like the ability to pass the full path to a test

/cc @nodejs/build @jbergstroem do you oppose to this being done?

[bnoordhuis]

Personally I'm fine with that as long as the current syntax (including wildcards like parallel/test-cluster-*) keeps working.

[MylesBorins]

I was imagining it could likely be a regex/replace for test/ and .js

Example implemented with sed

$ echo "test/parallel/test-cluster-worker-init.js" | sed 's+test/++; s/.js//'
parallel/test-cluster-worker-init

[reconbot]

This works https://github.com/nodejs/node/compare/master...reconbot:testpy-paths?expand=1 PR worthy?

[addaleax]

@reconbot It works, so I guess there’s nothing speaking against opening a PR and seeing where it goes? (You’ll want to add a tools: prefix to your commit subject line, btw; EDIT: and a Fixes: https://github.com/nodejs/node/issues/9684 line, too? :))

[reconbot]

I found the handy contributors guide link when opening the PR. I think I got it right

[jbergstroem]

I'm with @bnoordhuis; would accept such a PR.

[reconbot]

@addaleax thanks for the subsection btw, it wasn't clear to me what that should be