What steps will reproduce the problem? 1.

import org.specs.runner.JUnit4 import org.specs.{Specification, Scalacheck}

class SecondTest extends JUnit4(new Specification with Scalacheck { "foo" should { "equal foo" in { "foo" mustBe "bar" } } } )

2. Run the above with JUnit.
3. Look at the report.

What is the expected output? What do you see instead?

"foo should equal foo: foo should equal bar"

"equal foo"

What version of the product are you using? On what operating system?

Specs 1.3.1. Scala 2.7.1, Java 6, Ubuntu Hardy.

Please provide any additional information below.

I'm using Maven to run it.

Hi,

This is the "intended" behaviour since the display in Eclipse gives a readable display like:

foo should x equal foo | Failure: foo should equal bar

Yet, running the same test with maven doesn't provide the same readibility.

I'll try to find a find to differentiate between the runners and provide a better output.

I have fixed this issue by appending the system description before the example description.

Yet the failure description only shows up in the target/surefire-reports/*.txt files as it is the case with regular junit test cases.

It is committed in the latest version 1.3.2-SNAPSHOT (compatible with Scala-2.7.2-rc1 only).