commit 988bafd8d08916e30c93b4fa79d6e24a588a0401
Author: John Sanda
<jsanda@redhat.com>
Date: Tue Nov 9 16:33:44 2010 -0500
Fixing tests that were failing due to database clean up running
too soon
MetadataManager previously defined @BeforeClass and @AfterClass
methods for
setting up and tearing down each plugin meta data test class.
The database was
reset in the @BeforeClass method. Turns out that while the first
few test
methods of say OperationMetadataManagerBeanTest run, then before
the rest of its
test methods have executed the @BeforeClass method is executed
for say
ContentMetadataManagerBeanTest which wind up clearing out the
same test data
that OperationMetadataManagerBeanTest was using. To remedy the
situation, I
have made every configuration/test method in each
XXXMetadataManagerBeanTest
part of the plugin.metadata group. Then I changed the
@BeforeClass and
@AfterClass methods into @BeforeGroup and @AfterGroup methods
respectively,
esnuring that they only run once for the entire group.
* so by virtue of using the strategy of completely wiping out
the db, does this prevent
us from leverage testng to run our tests in parallel now? how
much slower does the
test suite execute in this branch versus master?