[
https://jira.jboss.org/browse/JBPM-2856?page=com.atlassian.jira.plugin.sy...
]
Huisheng Xu commented on JBPM-2856:
-----------------------------------
The ended execution won't store into the database. So in the assertExecutionEnded(),
we won't fetch any execution with state_ended. And I will add testcase for
parameter-out to verify this scenario. Thank you for noticing.
assertExecutionEnded should check for executions in STATE_ENDED
---------------------------------------------------------------
Key: JBPM-2856
URL:
https://jira.jboss.org/browse/JBPM-2856
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.3
Reporter: M M
Assignee: Huisheng Xu
Attachments: JBPM-2856-2010-05-16.patch, JBPM-2856.patch
In the testing framework, the method assertExecutionEnded() seems to have a bug in it. It
only checks whether a process instance has been deleted from the database. It should also
check for the case where a process instance has not been deleted from the database, but
has a state of Execution.STATE_ENDED.
It would look something like this:
public void assertExecutionEnded( final String processInstanceId )
{
final ProcessInstance pi = executionService.findProcessInstanceById(
processInstanceId );
assertTrue( "Error: an active process instance with id " +
processInstanceId + " was found", pi == null ||
Execution.STATE_ENDED.equals( pi.getState() ) );
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira