[
https://issues.apache.org/jira/browse/SCXML-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661381#action_12661381
]
Rahul Akolkar commented on SCXML-91:
------------------------------------
Summarizing the dev list discussion (hopefully the crimson check will not
require any more maintenance):
----
sebb wrote:
> but I think NSEs which are not caused by
> the faulty Sun 1.4 DOM should cause failures.
>
<snap/>
OK, so what you added to trunk does that. I guess we can retain the crimson
check as-is and keep refining it as and when it breaks with other obscure JDKs
and configurations you and I haven't tested on.
----
Looks like the major items on this issue are addressed?
> 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.
