[
http://jira.jboss.com/jira/browse/JBPM-1045?page=comments#action_12388588 ]
Aleksandar Kostadinov commented on JBPM-1045:
---------------------------------------------
Yes, exactly!
The modifications suggested aim report to show which tests are failing if any.
In certain situations currently, test suite fails. And due to not having exception thrown,
empty test report is generated. So we end up having no information what was wrong.
test suite has to trow a runtime exception on error so meaningful
report is generated
-------------------------------------------------------------------------------------
Key: JBPM-1045
URL:
http://jira.jboss.com/jira/browse/JBPM-1045
Project: JBoss jBPM
Issue Type: Bug
Reporter: Aleksandar Kostadinov
Assigned To: Tom Baeyens
Fix For: jBPM jPDL 3.2.3
When there are test suite initialization problems, test suite ignores exception (just
prints it to the output) that causes junit to crash.
I identified the issue in the following files:
jpdl/jar/src/test/java/org/jbpm/AllDBTests.java
jpdl/jar/src/test/java/org/jbpm/AllTests.java
have to have "throw t;" after "t.printStackTrace();"
As well the following test cases seem suspicious to me. I mean I'm not sure if an
exception by these tests will cause a test suite crash. Please inspect if trowing an
axception is desirable after printStackTrace method is used in these files:
./msg/command/AsyncExecutionDbTest.java
./perf/MemLeakTest.java
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira