You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by Adam Crain <ad...@plymouthsystems.com> on 2010/03/22 01:31:40 UTC
scalatest junit xml reporting
Hi,
I saw some comments on this from an earlier thread, but didn't see if
there was a resolution. Are there any flags associated with
test.using(:scalatest)
that override the default flat file reporting?
Scalatest has a number of reporting options:
http://www.scalatest.org/scaladoc/doc-1.0/org/scalatest/tools/Runner$obj
ect.html
including an XML reporting which I'm told is JUnit formatted. I'm trying
to get all of this integrated with Hudson.
FYI, I'm running off of edge & scalatest 1.0
Thanks,
Adam
Re: scalatest junit xml reporting
Posted by Alex Boisvert <al...@gmail.com>.
Hi Adam,
It's something I've been wanting to do so I just implemented it in trunk.
It will be in for our upcoming 1.4.0 release.
If you can't use trunk, you can use JUnit to run the tests and annotate your
classes with the
JUnitRunner<http://www.scalatest.org/scaladoc/doc-1.0/org/scalatest/junit/JUnitRunner.html>annotation
in the mean time.
alex
On Sun, Mar 21, 2010 at 5:31 PM, Adam Crain
<ad...@plymouthsystems.com>wrote:
> Hi,
>
> I saw some comments on this from an earlier thread, but didn't see if
> there was a resolution. Are there any flags associated with
>
>
>
> test.using(:scalatest)
>
>
>
> that override the default flat file reporting?
>
>
>
> Scalatest has a number of reporting options:
>
>
>
> http://www.scalatest.org/scaladoc/doc-1.0/org/scalatest/tools/Runner$obj
> ect.html<http://www.scalatest.org/scaladoc/doc-1.0/org/scalatest/tools/Runner$obj%0Aect.html>
>
>
>
> including an XML reporting which I'm told is JUnit formatted. I'm trying
> to get all of this integrated with Hudson.
>
>
>
> FYI, I'm running off of edge & scalatest 1.0
>
>
>
> Thanks,
>
> Adam
>
>
>
>
Re: seg faults due to rjb on linux
Posted by Bas Kok <ba...@gmail.com>.
Hi,
To solve this issue I also moved to JRuby, however quickly ran into new
issues while building a custom plugin that does process forking (which JRuby
doesn't support well).
However upgrading to a later ruby version (1.8 -> 1.9.1) fixed these issues
for me as well. Also colleagues of mine who are running 64bit linux don't
have the rjb issue.
Cheers,
--
Bas
On Mon, Mar 22, 2010 at 3:55 PM, Alex Boisvert <al...@gmail.com>wrote:
> Sadly, JRuby becomes your only viable choice at the moment. If startup
> time
> is an issue for you, try using it with nailgun.
>
> Alex
>
> On Mar 21, 2010 9:26 PM, "Adam Crain" <ad...@plymouthsystems.com>
> wrote:
>
> This is now biting me. I've found several posts to this issue. I get the
> seg faults when downloading dependencies.
>
> JDK 1.5 isn't an option b/c of some dependencies.
>
> Any suggestions? I'm using rjb 1.1.9 with buildr 1.3.5
>
> Thanks,
> Adam
>
Re: seg faults due to rjb on linux
Posted by Alex Boisvert <al...@gmail.com>.
Sadly, JRuby becomes your only viable choice at the moment. If startup time
is an issue for you, try using it with nailgun.
Alex
On Mar 21, 2010 9:26 PM, "Adam Crain" <ad...@plymouthsystems.com>
wrote:
This is now biting me. I've found several posts to this issue. I get the
seg faults when downloading dependencies.
JDK 1.5 isn't an option b/c of some dependencies.
Any suggestions? I'm using rjb 1.1.9 with buildr 1.3.5
Thanks,
Adam
seg faults due to rjb on linux
Posted by Adam Crain <ad...@plymouthsystems.com>.
This is now biting me. I've found several posts to this issue. I get the
seg faults when downloading dependencies.
JDK 1.5 isn't an option b/c of some dependencies.
Any suggestions? I'm using rjb 1.1.9 with buildr 1.3.5
Thanks,
Adam