You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by "Graham Turrell (JIRA)" <ji...@apache.org> on 2007/03/29 16:42:25 UTC

[jira] Closed: (WODEN-70) Running Woden test suite in network isolation mode

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

Graham Turrell closed WODEN-70.
-------------------------------

    Resolution: Fixed

Experience has shown that the clearest and cleanest way of testing successful isolation runs is to physically isolate the machine under test. Since our test suites are run manually and it is simple to isolate the test machine for a test run, this is probably no longer necessary. Should we ever fully automate our test suites then this is worth revisiting then, but no such plans exist at present. 

> Running Woden test suite in network isolation mode
> --------------------------------------------------
>
>                 Key: WODEN-70
>                 URL: https://issues.apache.org/jira/browse/WODEN-70
>             Project: Woden
>          Issue Type: Test
>          Components: Validation
>            Reporter: Graham Turrell
>             Fix For: M8
>
>
> 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)? 

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


---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org