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-275) Split out alltests.conf into several, smaller configurations
Date Fri, 13 Jan 2006 05:22:20 GMT
    [ http://issues.apache.org/jira/browse/JDO-275?page=comments#action_12362592 ] 

Craig Russell commented on JDO-275:
-----------------------------------

Some typos in the comments.

+    /* The total number of faiures. */
+    private int totalTestCount = 0;
+
+    /* The total number of faiures. */
+    private int totalFailureCount = 0;

Should be 
+    /* The total number of tests. */
+    private int totalTestCount = 0;
+
+    /* The total number of failures. */
+    private int totalFailureCount = 0;

I ran the tests with the new configuration files and got the same numbers. The new tests took
1 minute longer than the old tests (73 minutes vs. 72 minutes). Within the margin of error.

Good to go.


> Split out alltests.conf into several, smaller configurations
> ------------------------------------------------------------
>
>          Key: JDO-275
>          URL: http://issues.apache.org/jira/browse/JDO-275
>      Project: JDO
>         Type: Improvement
>   Components: tck20
>     Reporter: Michael Bouschen
>     Assignee: Michael Bouschen
>  Attachments: splitAllTests.patch
>
> Today alltests.conf lists all the JDO TCK test classes (execpt CompletenessTest) in one
big configuration. The idea is splitting it out into several, smaller configurations in order
to better tell where the problems are. I propose to have 11 new configuration replacing the
existing alltests.conf: 
> instancecallback.conf: 16 test classes with 16 test methods
>   org.apache.jdo.tck.instancecallbacks
> jdohelper.conf: 42 test classes with 43 test methods
>   org.apache.jdo.tck.api.jdohelper    
> pm.conf: 90 test classes with 90 test methods
>   org.apache.jdo.tck.api.persistencemanager
>   org.apache.jdo.tck.api.persistencemanager.cache
>   org.apache.jdo.tck.api.persistencemanager.close
>   org.apache.jdo.tck.api.persistencemanager.extent
>   org.apache.jdo.tck.api.persistencemanager.flags
>   org.apache.jdo.tck.api.persistencemanager.getobject
>   org.apache.jdo.tck.api.persistencemanager.lifecycle
> pmf.conf: 28 test classes with  37 test methods
>   org.apache.jdo.tck.api.persistencemanagerfactory
> enhancement.conf: 4 test classes with  31 test methods
>   org.apache.jdo.tck.enhancement
>   org.apache.jdo.tck.api.persistencecapable
> extents.conf: 13 test classes with 13 test methods
>   org.apache.jdo.tck.extents
> lifecycle.conf: 9 test classes with  12 test methods
>   org.apache.jdo.tck.lifecycle
> models.conf: 48 test classes with  49 test methods
>   org.apache.jdo.tck.models.embedded
>   org.apache.jdo.tck.models.fieldtypes
>   org.apache.jdo.tck.models.inheritance
> query.conf: 64 test classes with 138 test methods
>   org.apache.jdo.tck.query.api
>   org.apache.jdo.tck.query.delete
>   org.apache.jdo.tck.query.result
>   org.apache.jdo.tck.query.sql
> jdoql.conf: 81 test classes with 108 test methods
>   org.apache.jdo.tck.query.jdoql
> transactions.conf: 27 test classes with  27 test methods
>   org.apache.jdo.tck.transactions 

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