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] Commented: (JDO-147) Remove pm.deletePersistent from query tests
Date Fri, 02 Dec 2005 11:01:32 GMT
    [ http://issues.apache.org/jira/browse/JDO-147?page=comments#action_12359141 ] 

Michael Bouschen commented on JDO-147:

Oops, I forgot two comments:

- Class StringConcatenation defines a field parameters for the actual parameters of the test
queries. The first entry defines null as the actual parameter for te first query, but the
test query does not define any parameter.  
- In class DenoteUniquenessInFilter the comment  in the declaratuon of expectedResult does
not match the values use as expected result. Please check the test query and adapt the comment.

> Remove pm.deletePersistent from query tests
> -------------------------------------------
>          Key: JDO-147
>          URL: http://issues.apache.org/jira/browse/JDO-147
>      Project: JDO
>         Type: Bug
>   Components: tck20
>     Reporter: Michelle Caisse
>     Assignee: Michael Watzek
>  Attachments: JDO-147.patch
> The query tests delete the persistent instance that they create at the end of the test
using pm.deletePersistent().  Now that we use the new cleanup mechanism (addTearDownClass(Class)),
there is no reason to deletie the instance.  Also, the new maven option jdo.tck.cleanupaftertest
cannot override this cleanup, so you can never see the database contents for debugging.  Therefore,
we should remove the line that deletes the persistent instance.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message