If it were possible to invoke a CTL test suite using a RESTful API (as can be done with a TestNG-based suite) it would be much easier to hide the details about how a test suite is implemented and to facilitate interworking with test suites developed for WMS profiles (e.g. DGIWG, NSG).
The teamengine-spi-ctl module provides a CtlExecutor that can be used by a suite-specific controller. This is the same mechanism used by a TestNG suite. A profile ETS could then simply invoke the base ETS in this manner and merge the results.
A special main-auto.xml CTL script was added to exclude all tests that require manual intervention (these present a web form to a human "test oracle").
If it were possible to invoke a CTL test suite using a RESTful API (as can be done with a TestNG-based suite) it would be much easier to hide the details about how a test suite is implemented and to facilitate interworking with test suites developed for WMS profiles (e.g. DGIWG, NSG).
The teamengine-spi-ctl module provides a
CtlExecutor
that can be used by a suite-specific controller. This is the same mechanism used by a TestNG suite. A profile ETS could then simply invoke the base ETS in this manner and merge the results.