[WODEN-70] Running Woden test suite in network isolation mode

• Type: Test
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: M8
• Component/s: Validation
• Assignee: Unassigned
• Reporter: Graham Turrell
• Created: 06/Nov/06 23:09
• Updated: 29/Mar/07 14:41
• Resolved: 29/Mar/07 14:41

Description

An excellent validation of the a URI resolver is to run the entire test suite disconnected from the network. All external WSDL and XML Schema files referenced by the test suite much appear (directly or indirectly) in the Catalog used by the resolver under test, and local copies of those files must exist prior to test execution. With the current test suite, this applies to the W3C tests only.

Ideally there should be an ant task to automatically extract those files from the W3C external URLs, and build the catalog file. In the meantime they may be hard-wired into the Woden test suite (as the W3C tests currently are).

Also, decide upon and implement the means of running the tests in this mode. The Resolver and catalog are referenced at run-time via system properties. A JUnit test-suite could be created for each implemented Resolver to set properties accordingly, and call AllWodenTests.suite() in a simulated offline mode (eg. by "tampering" with http system properties).

Should the complete test-suite always be run multiple times (connected, and disconnected) for each supported Woden URI Resolver); or limit the offline tests to W3C tests only (by default at least)?