<joakim.ohlro...@gmail.com> wrote:
> Thanks for the tip, I would have to look into that I'm not that comfortable
> with the inner workings of buildr yet (or as cool people say: I'm a buildr
> n00b :)). At the moment buildr uses the ant-task which from what I
> understand is how things generally are done in buildr but it may be straight
> forward. Or is there a flag for the ant-task that gives the same behavior?

> /J

> On Tue, Sep 22, 2009 at 7:56 AM, Bill Venners <b...@artima.com> wrote:

>> Hi Joakim,

>> There's actually a method in org.scalatest.tools.Runner intended for
>> this use case. Runner has a main method and a run method. The run
>> method takes the same args as main, but returns a Boolean. Here's its
>> doc comment:

>> Runs a suite of tests, with optional GUI. See the main documentation
>> for this singleton object for the details. The difference between this
>> method and main is simply that this method will block until the run
>> has completed, aborted, or been stopped, and return true if all tests
>> executed and passed. In other words, if any test fails, or if any
>> suite aborts, or if the run aborts or is stopped, this method will
>> return false. This value is used, for example, by the ScalaTest ant
>> task to determine whether to continue the build if haltOnFailure is
>> set to true.

>> Does it sound like buildr could call this method directly?

>> Bill

>> On Mon, Sep 21, 2009 at 10:21 PM, Joakim Ohlrogge
>> <joakim.ohlro...@gmail.com> wrote:
>> > Absolutely. Basically I did three things:
>> > 1. The obvious thing, change the version to be downloaded by buildr to
>> > 1.0-for-scala-2.8.0-SNAPSHOT
>> > 2. Change the maven group from org.scala-tools.testing to org.scalatest
>> > These two changes were pretty straight forward though the group was not
>> > parameterized in buildr while I could probably get away with changing
>> > the
>> > scalatest-version by setting some variable in my project (but I didn't
>> > look
>> > into that, i just hacked the scala/tests.rb file directly.
>> > Now for the strangest thing I did: The buildr integration looked at
>> > scalatests console output to determine if any tests failed. Since the
>> > output
>> > looks a bit different when extending Spec I had to patch the condition
>> > that
>> > checked if the run had competed.
>> > 3. I changed the regexp: /Run completed\./ to  /(Run completed\.)|(All
>> > tests
>> > passed\.)/
>> > I meant to ask you what would be the best way to do this since the
>> > buildr
>> > integration I looked into (which is Daniel Spiewak's git-branch,
>> > unofficial
>> > and probably work in progress) seems a bit hacky. Buildr uses the
>> > ant-task
>> > under the hood, maybe I can get the same report output to file for all
>> > the
>> > different runners and it would be a more reliable strategy to parse
>> > those?
>> > Also the "completed" regexp seems to be there for this reason:
>> > # Parse for failures, errors, etc.
>> > # This is a bit of a pain right now because ScalaTest doesn't flush its
>> > # output synchronously before the Ant test finishes so we have to loop
>> > # and wait for an indication that the test run was completed.
>> > So a flush at the end of a run (if 1.0 does not already do this) would
>> > maybe
>> > speed things up a bit as well as relying only on the failure regexp:
>> > /(TEST FAILED -)|(RUN STOPPED)|(RUN ABORTED)/
>> > Which seems to work for the Spec style as well.
>> > I meant to commit my changes to my git-branch so any suggestions for
>> > improved strategies for failure detection etc would be most welcome.
>> > You can have a look at my clone here:
>> > http://github.com/johlrogge/buildr
>> > At the moment I have not pushed any changes back so it is identical to
>> > Daniel's clone.
>> > Hope this helps
>> > /J

>> > On Tue, Sep 22, 2009 at 2:53 AM, Bill Venners <b...@artima.com> wrote:

>> >> Hi Joakim,

>> >> A saw that you tweeted that with a patch to buildr you got this all
>> >> working under 2.8. Can you elaborate on what the patch was? I'd like
>> >> to understand what was needed.

>> >> Thanks.

>> >> Bill

>> >> On Mon, Sep 21, 2009 at 12:13 AM, Joakim Ohlrogge
>> >> <joakim.ohlro...@gmail.com> wrote:
>> >> > Tried it form eclipse and buildr. Works like charm (buildr reports
>> >> > that
>> >> > the
>> >> > tests fail but that seems to be a problem with failure detection in
>> >> > compination with using BDD-style (extends Spec)).
>> >> > Thanks for staying up to date (eclipse only has the latest nightly
>> >> > build
>> >> > available so new eclipse users will probably appreciate it :))

>> >> > On Mon, Sep 21, 2009 at 4:21 AM, Bill Venners <b...@artima.com>
>> >> > wrote:

>> >> >> Hi All,

>> >> >> I just released a fresh ScalaTest 1.0 snapshot, both for 2.7.5 and
>> >> >> the
>> >> >> latest nightly 2.8 build. Info on how to access it is here:

>> >> >> http://www.artima.com/scalatest/#snapshot

>> >> >> Some people have recently posted about trying to get ScalaTest 1.0
>> >> >> to
>> >> >> build under 2.8. It requires a few hand changes each time I do it,
>> >> >> because there is some code that simply won't compile under both 2.7
>> >> >> and 2.8. Each time I do this make a new branch, and from now on I
>> >> >> will
>> >> >> check in the changes I make to get it to build under 2.8. If you
>> >> >> want
>> >> >> to work with it, you can get tonight's build here:

>> >> >> svn checkout

>> >> >> https://scalatest.dev.java.net/svn/scalatest/branches/app/trunk-for-s...
>> >> >> --username guest

>> >> >> I compiled it with the latest 2.8 nightly build (downloaded today):

>> >> >> scala-2.8.0.r18678-b20090910020815

>> >> >> The only tasks remaining are more testing of the
>> >> >> org.scalatest.concurrent package, a bit more work in the
>> >> >> org.scalatest.mock package, and documentation. With luck the next
>> >> >> snapshot will be a release candidate. If you have time please give
>> >> >> it
>> >> >> a test drive and post feedback to scalatest-users.

>> >> >> Thanks.

>> >> >> Bill
>> >> >> ----
>> >> >> Bill Venners
>> >> >> Artima, Inc.
>> >> >> http://www.artima.com

>> >> > --
>> >> > -----------------------------------------------------
>> >> > Joakim Ohlrogge
>> >> > Agical AB
>> >> > Västerlånggatan 79, 2 tr
>> >> > 111 29 Stockholm, SWEDEN

>> >> > Mobile: +46-708-754004
>> >> > Blog: johlrogge.wordpress.com
>> >> > E-mail: joakim.ohlro...@agical.se

>> >> --
>> >> Bill Venners
>> >> Artima, Inc.
>> >> http://www.artima.com

>> > --
>> > -----------------------------------------------------
>> > Joakim Ohlrogge
>> > Agical AB
>> > Västerlånggatan 79, 2 tr
>> > 111 29 Stockholm, SWEDEN

>> > Mobile: +46-708-754004
>> > Blog: johlrogge.wordpress.com
>> > E-mail: joakim.ohlro...@agical.se

>> --
>> Bill Venners
>> Artima, Inc.
>> http://www.artima.com

> --
> -----------------------------------------------------
> Joakim Ohlrogge
> Agical AB
> Västerlånggatan 79, 2 tr
> 111 29 Stockholm, SWEDEN

> Mobile: +46-708-754004
> Blog: johlrogge.wordpress.com
> E-mail: joakim.ohlro...@agical.se