search

ericmckean / noop

Automatically exported from code.google.com/p/noop
Apache License 2.0
0 stars 0 forks source link

Buildr takes >30 seconds to run tests #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
We think this is because it invokes Ant once for every test suite. Using
ant is dumb, anyway, it's just convenient because ScalaTest has an ant task
to run the tests.

Ideally, while we're fixing the test runner, we would like the ant-junit
XML output, so our continuous build can say which tests failed and how many
tests we're running. Also, it would be great to get the spec report, so we
have a nice list of "the interpreter should read phrases" on every build.
Scalatest supports JUnit4 runner in the current snapshot release, which
might be a good way to go.

Original issue reported on code.google.com by aeagle22206 on 8 Sep 2009 at 5:38

GoogleCodeExporter commented 9 years ago 
Talked to Bill Venners, and Scalatest can produce the XML file itself as of 1.0.

Original comment by aeagle22206 on 18 Sep 2009 at 4:40

GoogleCodeExporter commented 9 years ago 
Upgrading to Buildr 1.4 fixes the problem, now invokes scalatest directly 
rather than 
with ant task

Original comment by aeagle22206 on 25 Nov 2009 at 11:25