I think our feature management story isn't smooth yet. We need to sort out some of the problems before proceeding.
1. Which repository we should use for test automation - Lets take RC release, p2-repo is not released and not available online. So we have to depend on local repo. To do that p2 repo should be available at the time of product build. But repo is not included to build and depends on certain product features like product samples and styles. Thus, repo will not be available at the product build time. To solve this problem we we need to build the repo before integration tests by excluding all product level dependencies. 2. All features are not available in each release. So this trend to test failures in future. E.g - You cannot install XACML features on API Manager 1.4.0. IS was not released with Carbon 4.1.0, so the relevant feature not available. A possible solution would be to filter available features and skip tests based on feature availability. However you can start writing tests using online p2-repo (4.2.0) until we sort out above mentioned problematic areas. Thanks, Krishantha. On Mon, Sep 9, 2013 at 5:42 PM, Supun Malinga <[email protected]> wrote: > Hi, > > great! thanks, > > On Mon, Sep 9, 2013 at 5:38 PM, Dharshana Warusavitharana < > [email protected]> wrote: > >> Hi Supun, >> >> Yes this feature is supported. But still you need to figure out how you >> will handle the repo location inside your test. >> > > you mean giving the relevant p2-repo url right?. In that case we can > manage that at automation-framework level, since the repo is unique to each > platform version. > > thanks, > >> >> The automation API provides a client for installing features is " >> FeatureManagementAdminServiceClient<https://svn.wso2.org/repos/wso2/people/dharshana/automation/framework/test-automation-framework/org.wso2.carbon.automation.api/src/main/java/org/wso2/carbon/automation/api/clients/feature/mgt/FeatureManagementAdminServiceClient.java>" >> available on [1]. >> And sample test case to use it is available on [2]. >> >> [1]. >> https://svn.wso2.org/repos/wso2/people/dharshana/automation/framework/test-automation-framework/org.wso2.carbon.automation.api/src/main/java/org/wso2/carbon/automation/api/clients/feature/mgt/FeatureManagementAdminServiceClient.java >> [2]. >> https://svn.wso2.org/repos/wso2/people/dharshana/automation/esb-hackathon/esb/esb/4.7.0/modules/integration/tests/src/test/java/org/wso2/carbon/esb/hl7/transport/test/HL7TestCase.java >> >> Thank You, >> Dharshana. >> >> >> On Mon, Sep 9, 2013 at 5:33 PM, Supun Malinga <[email protected]> wrote: >> >>> Hi All, >>> >>> Do we have support for this from the automation framework?. >>> >>> Since j2ee features are not shipped with AS by default, we would need to >>> install j2ee features at integration tests to run j2ee tests. Can we get a >>> sample test case if this is already available or we need add this as an >>> improvement to the automation-framework. >>> >>> thanks, >>> -- >>> Supun Malinga, >>> >>> Senior Software Engineer, >>> WSO2 Inc. >>> http://wso2.com >>> http://wso2.org >>> email - [email protected] <[email protected]> >>> mobile - 071 56 91 321 >>> >> >> >> >> -- >> >> Dharshana Warusavitharana >> Senior Software Engineer , Test Automation >> WSO2 Inc. http://wso2.com >> email : [email protected] <[email protected]> >> Tel : +94 11 214 5345 <94112145345> >> Fax :+94 11 2145300 >> cell : +94772202595 >> blog : http://dharshanaw.blogspot.com >> >> lean . enterprise . middleware >> > > > > -- > Supun Malinga, > > Senior Software Engineer, > WSO2 Inc. > http://wso2.com > http://wso2.org > email - [email protected] <[email protected]> > mobile - 071 56 91 321 >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
