[
https://issues.apache.org/jira/browse/ODFTOOLKIT-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460156#comment-13460156
]
DaLi Liu commented on ODFTOOLKIT-152:
-------------------------------------
Verified status of this issue
2.not sure - I am not sure about this issue, maybe still need to be opened
> Need to integrate validation/conformance testing with unit tests
> ----------------------------------------------------------------
>
> Key: ODFTOOLKIT-152
> URL: https://issues.apache.org/jira/browse/ODFTOOLKIT-152
> Project: ODF Toolkit
> Issue Type: Bug
> Components: java
> Affects Versions: 0.8.6
> Environment: Operating System: Windows
> Platform: PC
> Reporter: Robert Weir
> Assignee: issues
> Fix For: 0.9
>
>
> We're starting to see some ODFDOM-generated files that are not valid
> according to the latest schemas. I think we will all agree that this is not
> good.
> One thing we can do to detect these types of problems earlier is to make sure
> that we run the ODF Validator against every test file that is created as part
> of the unit tests.
> 1) We should use a command-line version of the validator
> 2) We should make sure that the validator uses the same version of the ODF
> schema that ODFDOM uses for codegen. It is important that these are in sync,
> even if they are not the very latest versions.
> 3)We should run the validator against each document created in the unit
> tests. One elegant way to do this is to create a custom Ant task for running
> the validator.
> 4) Goal should be for all unit tests to generate only conforming ODF
> documents, according to whatever revision of the schema we are using.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
