You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been following the style of using multiple independent test files in test dir : tap ./test/*.js .
Assuming that this style is common it would be nice to be able to do cover run test/*js instead of restricting the command to a single js file.
Do you think that this enhancement make sense?
By the way node-tap's own "experimental" code coverage functionality (which never worked for me) does allow multiple source files as inputs.
The text was updated successfully, but these errors were encountered:
@ogt that's an interesting thought. The way I usually achieve this is by having a single test runner that will run the other files, rather than executing each individually. I know node-tap prefers a more isolated approach, where it is forking a new process per file (which is how it does its experimental coverage).
I have been following the style of using multiple independent test files in test dir :
tap ./test/*.js
.Assuming that this style is common it would be nice to be able to do
cover run test/*js
instead of restricting the command to a single js file.Do you think that this enhancement make sense?
By the way node-tap's own "experimental" code coverage functionality (which never worked for me) does allow multiple source files as inputs.
The text was updated successfully, but these errors were encountered: