Re: [jboss-as7-dev] AS7 testsuite extension

Hi Brian, thank you for your reply, comments are inline. Agree, submodules should be named domain-http, domain-cli, domain-java, standalone-http, standalone-cli and standalone-java. Maybe one submodules for shared tests and resources. So we should propose some changes for this module, it's currently running against one standalone server and contains only one test. I think testsuite/clustering will have several submodules to cover different scenarios, positive test can have server execution automatically managed by ARQ. Negative tests (failovers) must have server execution managed by ARQ but controlled from testscases (ARQ-336 [1], FailoverTestCase.java [2]). OK, I agree with that, DC is only about server management, no effect on AS7 functionality. My point about ARQ with DC support is more about message to users, we really recommend to use DC, but we don't use it in our tests ... Several standalone server in cluster are sufficient to verify that clustering functionality is working properly. But I steel need ARQ to start DC (using managed mode). Could you please explain how do you mean your note? We don't want to store configuration xml files in repository, we would like to prepare necessary configuration using management API. We have quite bad experience with configuration stored in xml files for testing, at least when development is still going on. Plan is to keep "prepare servers" as simple as possible. But still I want to have appropriate prepare module for each test module to keep it straightforward when searching for possible problem - in one module is configured server and in second is test which should work. If I'm not wrong, pointing ARQ to custom configuration xml file can be done in arquillian.xml by defining element property named serverConfig under configuration element. -- Rostislav Svoboda JBoss QA, Brno [1] https://issues.jboss.org/browse/ARQ-336 [2] https://github.com/mgencur/edg-tests/blob/master/failover/src/test/java/o...