You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Rahul Akolkar (JIRA)" <ji...@apache.org> on 2008/12/03 21:39:44 UTC

[jira] Updated: (SCXML-98) TestCases should use SCXMLParser

     [ https://issues.apache.org/jira/browse/SCXML-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rahul Akolkar updated SCXML-98:
-------------------------------

    Affects Version/s:     (was: 0.8)
                       0.9
        Fix Version/s: 0.10

We already do that in the J6 branch:  http://svn.apache.org/repos/asf/commons/proper/scxml/branches/J6/

We do some of that in trunk (newer tests use the SCXMLParser). It might be better to port most of the tests to use the SCXMLParser as you say, but I'd leave a couple for the SCXMLDigester as well (we want to test it even if its deprecated, until it is removed in v1.0).

Please provide a patch to move more tests in trunk to using the SCXMLParser if possible (necessary changes to the test cases can be seen in the J6 branch, so its mostly a matter of porting changes to trunk).

Tentatively setting fix version to next release v0.10.


> TestCases should use SCXMLParser
> --------------------------------
>
>                 Key: SCXML-98
>                 URL: https://issues.apache.org/jira/browse/SCXML-98
>             Project: Commons SCXML
>          Issue Type: Bug
>    Affects Versions: 0.9
>            Reporter: Ingmar Kliche
>             Fix For: 0.10
>
>
> The SCXMLParser implements the latest SCXML parsing rules, whereas the SCXMLDigester is deprecated. But a lot of testcases still rely on the SCXMLDigester (indirectly) by using SCXMLTestHelper::getExecutor(url). The testHelper implementation should use the SCXMLParser.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.