[
https://issues.apache.org/jira/browse/DAFFODIL-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-2424.
-----------------------------------
Feature being deprecated per dev. Closing in lieu of DAFFODIL-2535.
> Add CatalogManager.properties tests
> -----------------------------------
>
> Key: DAFFODIL-2424
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2424
> Project: Daffodil
> Issue Type: Test
> Components: QA
> Reporter: Steve Lawrence
> Priority: Minor
> Fix For: 3.2.0
>
>
> Daffodil has a capability to use a CatalogManager.properties file to specify
> XML catalogs for resolving includes. We do not have many, if any, tests that
> verify that this functions as expected. This is partly because it is
> difficult to write tests because the CatalogManager.properties file must be
> at the root of the classpath, so one test could affect other tests.
> We probably need a way to fork tests that deal with CatalogManager.properties
> so that we can fork different tests in different temprory directories that
> contain different CatalogManager.properties files. Perhaps the CLI
> integration tests are a good candidate for this, but it might make testing
> some circumstatnces more difficult.
> For reference, the TestDaffodilXMLLoader.scala file had tests that verified
> CatalogManager.properties behavior. But in some cases the tests would be
> skipped, and they were not thread safe when they were run. So these tests
> were removed. See the below link to see these tests before they were removed.
> These tests are good candidates as a starting point for what kinds of tests
> would be useful to add:
> https://github.com/apache/incubator-daffodil/blob/0391ba1345521ce2119833391428a626728b7df3/daffodil-test/src/test/scala/org/apache/daffodil/xml/test/unit/TestDaffodilXMLLoader.scala
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
