[
https://jira.jboss.org/jira/browse/JBPM-1733?page=com.atlassian.jira.plug...
]
Thomas Diesler resolved JBPM-1733.
----------------------------------
Fix Version/s: jBPM 3.3.0 CR1
(was: jBPM 3.3.0)
Resolution: Done
The AbstractDbTestCase now verifies that there are no records left on tearDown().
Delegating DB cleanup to setUp() of N+1 is not advisable. Only test N can know what
records need to be removed and how.
createSchema is called for every DB test
----------------------------------------
Key: JBPM-1733
URL:
https://jira.jboss.org/jira/browse/JBPM-1733
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jPDL 3
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Priority: Blocker
Fix For: jBPM 3.3.0 CR1
This issue prevents meaningful test runs on postgresql
hsqldb: 1.5 min
mysql: 25min
postgre: 5h
public void setUp() throws Exception
{
log.debug("### starting " + getLongName() + "
####################################################");
super.setUp();
try
{
// TODO: This creates the schema on EVERY test
createSchema();
// If a clean DB is realy needed this should perhaps be done
//cleanSchema();
createJbpmContext();
initializeMembers();
}
catch (Exception ex)
{
// Note, that if setUp fails a call to tearDown will not happen.
log.error("Exception is setUp, tearDown will not get called", ex);
throw ex;
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira