Hi Lakshman, In kernel OSGi tests, each test class has its own configurations. So the test distribution will be different from class to class even though the base distribution is same. So we have to start test distribution for each and every class since we can not change the configurations at the runtime. If we use PerSuite strategy, then the distribution will start only once and the configuration will be same for all the classes.
For example, test[1] and [2] you can see that there are different set of test artifacts to be installed in order to test for two different scenarios. And also, if the test distribution is same for two test classes, then there is no point of having two separate classes and instead of that, all the methods can be written inside one single test class. [1] https://github.com/wso2/carbon-kernel/blob/master/tests/osgi-tests/src/test/java/org/wso2/carbon/osgi/startupresolver/DynamicCapabilityOSGiTest.java [2] https://github.com/wso2/carbon-kernel/blob/master/tests/osgi-tests/src/test/java/org/wso2/carbon/osgi/startupresolver/MultipleCapabilitiesForCapabilityListenerOSGiTest.java Thanks, Chanaka. On Tue, Apr 18, 2017 at 8:01 PM, Lakshman Udayakantha <[email protected]> wrote: > Hi, > > We have used PerClass ExamReactorStrategy as the default strategy. This > means test distribution will start for every class in the test suite. Is > there any particular reason to select that strategy? This will increase the > build time when the test class space grows. So we can go with PerSuite as > the default strategy to reduce the build time. WDYT? > > Thanks, > Lakshman. > > -- > Lakshman Udayakantha > WSO2 Inc. www.wso2.com > lean.enterprise.middleware > Mobile: *0717429601* > > -- Chanaka Cooray Software Engineer, WSO2 Inc. http://wso2.com Email: [email protected] Mobile: +94713149860 <https://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
