You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jdo-dev@db.apache.org by "Craig Russell (JIRA)" <ji...@apache.org> on 2005/09/21 03:31:28 UTC

[jira] Updated: (JDO-140) Add get/setRollbackOnly tests

     [ http://issues.apache.org/jira/browse/JDO-140?page=all ]

Craig Russell updated JDO-140:
------------------------------

    Attachment: jdo140patch.txt

These are the two test cases in patch format.

> Add get/setRollbackOnly tests
> -----------------------------
>
>          Key: JDO-140
>          URL: http://issues.apache.org/jira/browse/JDO-140
>      Project: JDO
>         Type: Test
>   Components: tck20
>  Environment: TCK
>     Reporter: Craig Russell
>     Assignee: Craig Russell
>  Attachments: jdo140patch.txt
>
> There are two test classes for get/setRollbackOnly.
> One test class transactions.AfterSetRollbackOnlyCommitFails tests assertion A13.4.5-1 
> Once a transaction has been marked for rollback via setRollbackOnly, the commit method will always fail with JDOFatalDataStoreException. 
> The strategy is to begin a transaction, set rollback only, and commit. The expected behavior is to catch an exception.
> The second test class transactions.GetRollbackOnlyReturnsFalseUntilSet tests assertion A13.4.5-2
> After a transaction is begun, getRollbackOnly will return false until set commit or rollback is called.
> The strategy is to begin a transaction, test that getRollbackOnly is false, setRollbackOnly, and test that getRollbackOnly is true.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira