Allow nodeunit to run tests in a dir and recursively inside its child dirs

[aurium]

I'm using nodeunit in a project and i'm very happy with it, but my collection of test modules is going to be enough big to convince me to organize then in sub-directories. I start to do this, but i discover that "nodeunit test" command will not to run tests inside "test/helpers" or "test/models", so i made a patch to make util.modulePaths() to get it recursively to nodeunit.runFiles().

I don't see why not to work recursively, so i think that is the better default action.

I also made it with synchronous fileSystem methods because the testing action is not paralleled and the asynchronous code to do this is crazily more complex. :-)

[caolan]

I think this is a good idea, but should include 2 changes:

1. This should be made an option (-r perhaps) since we might break existing test suites by running fixtures directories etc.
2. Nodeunit makes use of the async library which will help with the complexity of reading directories asynchronously, so we should remove the sync call - I can help with this

Hopefully these changes would be acceptable?
When I get some time to work on this I can make these changes and merge this in.

Thanks again for your contribution :)

[aurium]

Thank you!
And i see, i will learn when i see the result code with your adaptation. :-)

[Sannis]

I hope I will help with this issue in next week.

Maybe we can use nopt to parse arguments? It installs with npm, so it does not be a problem for node users.

[mreinstein]

@aurium I think this is a good patch. Can you please update your patch and resubmit? It doesn't merge cleanly.

[achingbrain]

It would be rather good if something like this made it in. I frequently find myself arranging tests in subdirectories that mirrors the code they are testing and then being unable to run all the tests in one go without having some sort of test aggregator.

[groe]

+1

[mariansollmann]

👍

[rpaterson]

+1

[jarrettchisholm]

+1

[bud-mo]

+1

[alexgandy]

+1

[Petah]

+1

[zoejobson]

+1

[terodox]

+1

[mreinstein]

Sorry for the incredibly long reply delay!

I think #308 is a good solution. Waiting for the re-submission of the PR which merges cleanly and includes tests.

[mreinstein]

resolved via #308