Hi, On Tue, 2009-02-17 at 18:51 -0600, Rhett Sutphin wrote: [snip] > Another solution to that problem would be to have an option to only > run the tests for a single module -- sort of like test:pattern, except > that the constraint would be the module. This would help with another > minor issue I've noticed: when you specify a pattern, all the tests in > all the modules that match that pattern are run, even if you invoke > test (or integration) from a submodule. I would also expect that, when running tests from within a specific (sub-)module, only tests of this module are executed. Even if other modules depend on the current one, I would not expect that tests of the dependent module are run.
What is the reason that tests of all modules are run? Cheers, Martin > Pattern execution appears to > ignore the successful test check, too. The case where this has been a > problem for me is running integration tests. I have several > integration tests with "activity" in the filename. I also have a > large number of unit tests with activity in their filenames. So if I > want to run just the integration tests for "activity," I have to wait > for several dozen unit tests, across several other modules, to complete. > > The latter issue is less of a problem than the former, but I mention > it since they have a possible common solution. Is there an existing > solution for any of these? > > Thanks, > Rhett > >
signature.asc
Description: This is a digitally signed message part
