db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-188) Add tests for static JDOHelper.getObjectIds methods
Date Thu, 27 Oct 2005 08:03:57 GMT
    [ http://issues.apache.org/jira/browse/JDO-188?page=comments#action_12356054 ] 

Craig Russell commented on JDO-188:

You are right.

The new methods are indeed in JDOHelper not in PersistenceManager. So the test needs to be
written for the JDOHelper class.

I'd propose the new test case api.jdohelper.GetObjectIds with test methods testGetObjectIdsCollection
and testGetObjectIdsArray. The collection of parameter objects should include null, transient
instances, and persistent instances from multiple persistence managers. 

The JDOHelper checked into the repository does not include the new methods, so as part of
this work the methods need to be added.

> Add tests for static JDOHelper.getObjectIds methods
> ---------------------------------------------------
>          Key: JDO-188
>          URL: http://issues.apache.org/jira/browse/JDO-188
>      Project: JDO
>         Type: Test
>   Components: tck20
>  Environment: TCK
>     Reporter: Craig Russell

> A8.3-11 [static Object[] getObjectIds (Object[] pcs); static Collection getObjectIds
(Collection pcs); These methods return the JDO identities of the parameter instances. For
each instance in the parameter, the getObjectId method is called. They return one identity
instance for each persistence-capable instance in the parameter. The order of iteration of
the returned Collection exactly matches the order of iteration of the parameter Collection].
> The test case api.persistencemanager.GetObjectIds needs a test method per API. 
> The setUp method creates 50 persistent instances of type PCPoint and stores the ids in
an ArrayList and the instances in a separate ArrayList. The test case call getObjectIds and
verify that the object ids returned match the objects ids that are in the list.
> There are no negative tests.

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