|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
|
|
Environment:
|
TCK
|
|
| Resolution Date: |
23/Apr/06 03:10 AM
|
|
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.
|
|
Description
|
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. |
Show » |
| No work has yet been logged on this issue.
|
|
Test
Closed
Major
Add get/setRollbackOnly tests
