Hi I am working on $subject. Our aim is to decrease the ESB server stress while tests are executing. Currently around 900 test cases in one module named tests are running against a one ESB server started by test framework and it takes nearly two hours to complete all test cases. In all the test cases there are lots of admin services callings , service invocations , server configurations (axis2.xml) and server restart calling happens every time. Sometimes it will introduce some intermittent test failures. So breaking the tests modules will ease of running test cases and debugging test failures.
So we tried to break down the Integration tests into 5 modules as mentioned bellow! 1) tests-services - Proxy, Security, Endpoint, Sequence, Localentry, Rest, jaxrs, schedule task related test cases 2) tests-mediators - Test Cases related to mediators, message processors, message stores, priority executors 3) tests-transports - JMS,VFS, Nhttp, PTT, VFS,TCP, HL7, .... etc related test cases 4) tests-samples - ESB sample related test cases 5) tests-others - Other test cases Then in each of module, test framework starts a fresh ESB server and test are being executed against that server. But there are few concerns we have to consider 1) We can guarantee the number of test cases and time to complete running in each module are same . Those count varies from module to module since some modules have more test cases. 2) It needs the space more than a space used tests module. 3) Need to review 5 test reports Really appreciate your ideas for above structure for integration test for ESB to continue the work. Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
