db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JDO-139) Issues with tck20 test case transaction.GetOptimistic
Date Tue, 20 Sep 2005 21:34:27 GMT
     [ http://issues.apache.org/jira/browse/JDO-139?page=all ]
     
Michael Bouschen resolved JDO-139:
----------------------------------

    Resolution: Fixed

I removed class GetOptimistic and updated the assertion spreadsheet. 
I also updated class Rollback to not refer the query test class anymore.

> Issues with tck20 test case transaction.GetOptimistic
> -----------------------------------------------------
>
>          Key: JDO-139
>          URL: http://issues.apache.org/jira/browse/JDO-139
>      Project: JDO
>         Type: Bug
>   Components: tck20
>     Reporter: Michael Bouschen
>     Assignee: Michael Bouschen
>     Priority: Minor

>
> There are a couple of issues with the test class org.apache.jdo.tck.transactions.GetOptimistic:
> - It passes the query test class BoundParameterCheck to BatchTestRunner.run in  the main
method. Class transactions.Rollback has the same issue.
> - It refers assertion A13.4.1-2 in the class javadoc, but this assertion is about Transaction.isActive.
> - The correct assertion is A13.4.2-13 which is marked as duplicate of 5.8 in the assertions
spreadsheet.

-- 
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


Mime
View raw message