Yes, please check in the worksheet as you have it. Craig
On Mar 29, 2006, at 11:43 AM, Michelle Caisse wrote:
Craig L Russell wrote:What I'd recommend is that - the StateTransition tests only refer to A5.9.1..190, which denotes the global state transition table in the spec and that - we mark all other state-transition related assertions in the lifecycle tab of the spreadsheets as duplicates of A5.9.1..190, as is done for a few (but not all).This sounds like a reasonable approach. I don't know if there is value in adding duplicate assertions to the test cases. I think these can be handled by referring the duplicates to the state transition section of the assertion spreadsheet.Would it be best if I check in the spreadsheet with my current changes so you can then mark the appropriate assertions as duplicates? I may need to make some further changes after you are done to update the count of tested assertions.-- Michelle
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
