[
https://issues.apache.org/jira/browse/SCXML-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660740#action_12660740
]
Sebb commented on SCXML-91:
---------------------------
SCXMLTestHelper has now been updated in J6 to throw Exceptions:
URL: http://svn.apache.org/viewvc?rev=731386&view=rev
Log:
Prepare for changes to SCXMLTestHelper
URL: http://svn.apache.org/viewvc?rev=731387&view=rev
Log:
Remove try/catch blocks for Exceptions that are not expected in testing
In trunk, the same changes have been made, except that DOM serialisation errors
are allowed through
(which is closer to what I would like to see):
URL: http://svn.apache.org/viewvc?rev=731393&view=rev
Log:
Prepare for changes to SCXMLTestHelper
URL: http://svn.apache.org/viewvc?rev=731543&view=rev
Log:
Remove try/catch blocks for Exceptions that are not expected in testing
Improve non-serialisable check so it only allows DOM elements to fail
> Test case bugs
> --------------
>
> Key: SCXML-91
> URL: https://issues.apache.org/jira/browse/SCXML-91
> Project: Commons SCXML
> Issue Type: Bug
> Affects Versions: 0.9
> Reporter: Sebb
> Fix For: 0.10
>
>
> Test cases are difficult to debug if they fail.
> This is because many test cases catch Exception, and don't report it fully.
> Test cases should only catch a (specific) Exception if the test is expected
> to generate one, and should otherwise throw the Exception.
> Several test cases report problems to System.out or System.err and carry on
> processing.
> For example, serialisation errors are largely ignored, and
> SCXMLTestHelper#testExecutorSerializability() ignores IO errors.
> Testing generates a lot of output, some of which appears to be errors (e.g.
> stack traces) yet the test passes.
> Ideally tests should suppress output stack traces which are expected during
> testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
