Sorry, lots of questions these days.<br><br>Is there a normal approach for preconditions? In JUnit, I might put a few assertions in the setUp() just to make sure that the test 'data' I've created meets expectations before going to test it.
<br><br>So, for instance, I've got an object that is audited using acts_as_audited and I'd like to test the XML that results from model.revisions.to_xml(). I've created the object and modified it twice, so I expect there to be three revisions, as far as the test goes. It's not really a 'spec', because it's not part of the contract that model objects have three revisions, it's just something I want to make sure is true before I run off and conduct some tests.
<br><br>I could raise an exception in the before block if the precondition isn't met, any other choices?<br clear="all"><br> - Geoffrey<br>-- <br>Geoffrey Wiseman<br>