@m13m
@vil1 Awesome!
Whichever the main scalaz/scalaz repo operates under, testz does
Among changes: now there's no need for a distinct harness interface for specs2, making it easier to write tests that work for specs2, scalatest and testz without depending on anything more than testz-core
Also a lot of documentation in the docs/ folder, still need to build it and get it up on gh-pages though
@here testz now has documentation on github pages (and a new release: 0.0.5); you can read it at http://scalaz.github.io/testz. I've tried to document every line of (non-test) code in testz; please let me know if there are any oversights.
fun fact :
testz.assert tends to disturb some people who confuse it with scala.Predef.assert and therefore find it not very FP-ish
@edmundnoble is this legal? or should I be ashamed and banned?
def sneakyHarness[T](self: Harness[T]): Harness[T] =
new Harness[T] {
def test(name: String)(assertions: () => Result): T =
self.test(name) { () =>
try {
assertions()
} catch {
case _: NotImplementedError =>
Fail()
case ex: Exception =>
ex.printStackTrace()
Fail()
}
}
...
}
Well, you should probably be ashamed and banned
But that's irrelevant here ;)
If you have a lot of code which can fail with exceptions, you can go ahead and do that. In general though, I think for most code throwing an exception is an irrecoverable failure for the rest of the tests.
There are exceptions to this.
FutureHarness and TaskHarness catch exceptions, but not in this way; only inside the Task or Future context.
This means that if you take a
FutureHarness and convert it to a Harness, there is no observable difference between that and PureHarness as a Harness.
I was just about to add tests for this for
TaskHarness, actually, which are instructive: scalaz/testz#27
New testz PR, changing around the primitives somewhat to make them easier to manipulate. Comes with
scalaz/testz#28
TestOnly, for doing... exactly what it sounds like ;)scalaz/testz#28
It might one day. Don't lose hope.
bless you, testz
I'm not convinced that failure messages are something we shouldn't support.
You can also provide an EffectHarness which returns results in
Writer or something.
@edmundnoble are you planning on keeping this project under the scalaz org?
