I see...
Wouldn't it be good to add "fail" and "skip" alias methods for
providing compatibility with ScalaTest and Specs?
As a library author I'd like to leave the decision, which test
framework to use, to my users and still provide some test support
code.
The easiest way, which so far (with Specs 1, ScalaTest, TestNG, JUnit)
worked nicely, was to have a `TestSupport` trait that you can mix into
your tests:
trait TestSupport {
this: { def fail(msg: String): Nothing } =>
...
}
This trait can be mixed into all test classes from frameworks that
define a `fail` method taking a String.
All major frameworks do this, except (so far) specs2.
If you decide that two or three more aliases would clutter up the
Specs2 API too much I'll have to resort to some structural type class
solution, which would probably still work but introduce more overhead.
What do you think?
Cheers,
Mathias