Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Taking multiple test files as argument #37

Open
ogt opened this issue Apr 29, 2013 · 1 comment
Open

Taking multiple test files as argument #37

ogt opened this issue Apr 29, 2013 · 1 comment

Comments

@ogt
Copy link

ogt commented Apr 29, 2013

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.

@itay
Copy link
Owner

itay commented Apr 29, 2013

@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).

Happy to take a pull request to allow this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants