Perfect, Finn! I've just hacked together a little test extension that
lets me evaluate properties and write failure messages to a singleton
which a JUnit test case could process. It's very rough right now, but
with a little more work this could really be cool for checking the FO
Looks very good.
How about adding a property
expected-outcome="success|fail" (with a default of "success")
to <test:assert>, <eval> and <true> tags and when the value is "fail",
print "Expected failure still fails as expected"
throw "Expected failure was miraculously solved!!!"
That way test for unimplemented features can be added without having to
disable the entire test file.