On Tue, Jan 8, 2008 at 6:53 PM, Tim Hicks <tim@...> wrote:
> Derek Richardson wrote:
> > > tests are taking about 12-15 minutes to run on my laptop, which makes
> > > progress here *very* slow :(.
> > >
> >
> > Combinatorial explosion of the testing procedure. Yes, they take a
> > long time even on my quadcore. Needs to be fixed.0
> >
>
>  Ok, I've managed to figure out how to setup the feed config - i.e. my
> problem in my last email - but now I'm really bumping up against this issue
> of *long* test runs.
>
>  I need to run my tests repeatedly to keep trying things out, adding more
> test coverage, etc.  However, each test run is currently taking circa 20-25
> minutes to run.  As someone with limited time to spend on this, and time
> that only comes up in chunks of a few hours, this is pretty debilitating
> from the point of view of making it possible to contribute :(.
> ...
>  At root, can anyone help me figure out how to either (a) disable the long
> running tests, (b) make them not long running?

Sorry it took so long to address this. I've cut test time by > half,
they run in 2 minutes on my macbook pro. Even coverage reports now run
in < 20 mins. Still too long, but better.

The tests are like plone - they're not slow, they do a lot! The
problem is that these are all ftests, not unit tests. I mean, it's
good to have lots of good ftests, they just take a while to run.

Short-term solution: put your tests in a different test file and run
it with "bin/instance test -s vice.plone.outbound -t <name of test
file>". This will only run *your* test, instead of all the tests.
It'll be nice and zippy and you can simply run all the tests once,
before you ci, to make sure nothing is broken anywhere else.

Derek