Support regexes for `:include` and `:exclude` terms about boot-test

[seancorfield]

No, I ran some tests with this patch in place and the total time was about 49s without the patch (and using filters) and 45s with the patch (and using include). The pod stuff is a huge time sink, but it's a fairly static overhead -- and for those of us who need the isolation of pods to run tests with different sets of dependencies :)

Mostly the issue is that for any given set of tests I want to run, I don't want all my namespaces loaded -- I just want the subset loaded that my selected tests will load.

[seancorfield]

This can be closed now as PR #30 provides this and was just merged in (thank you!).

[arichiardi]

I started working on this one a bit, but at the moment the :namespaces option is necessary for the test task: it is an --include already. So I was thinking of proposing the alternative that I implemented in boot.test (core).

If :namespaces is not there, we include all the tests on the classpath and by doing this now we can have --include and --exclude (or --invert) set of regexes to be on par with the other boot tasks.

How does it sound?

[crisptrutski]

Sounds good to me! We should probably ping an adzerker though :)

[daveyarwood]

Sorry I'm late to the party. @arichiardi 's idea sounds good to me, let's do it!

[seancorfield]

Note that boot-expectations uses include / exclude as regexes to filter namespaces before even trying to require them. boot-test today requires all namespaces unless you specify a complete set of namespaces to load.

The problem with filters is that it filters the Vars after requiring all the namespaces.

I'd be happy to send a PR for -I / --include / -X / --exclude to match boot-expectations as regexes to filter the names of namespaces prior to requiring them.

[arichiardi]

Probably the above is also the reason why tests are kind of slow, I would love to see a patch then.