Hi Pradeep, Regarding this in clarity so far we have not consider feature installation and carbon bundle level scenarios. But still general idea here is to verify the functionality of particular feature with the given product, then we can move forward with clarity.
We can initiate the feature installation module before test state and proceed with the test case. For newer approach of the builder we can initiate product as a node and move for ward with given tests if particular feature is available in feature list. We can further discuss on this . As Abstract we can use clarity for this with introducing feature installation capability to the Clarity. Thank You, Dharshana. On Fri, Feb 1, 2013 at 12:04 AM, Dileepa Jayakody <[email protected]> wrote: > > > On Thu, Jan 31, 2013 at 11:49 PM, Pradeep Fernando <[email protected]>wrote: > >> >> >> >> On Thu, Jan 31, 2013 at 11:44 PM, Amila Maha Arachchi <[email protected]>wrote: >> >>> Hi Pradeep, >>> >>> Seems like a good thing to consider. Do you mean to run these tests >>> during the build time (integration tests) or against a built pack (by using >>> the test automation binary pack)? >>> >> >> the latter seems to be way to proceed. But I'm not sure. Open for ideas. >> :) >> > > +1 for running against built packs and the platform p2-repo. > This way we can iteratively test the p2-repo against all product > combinations for resolution conflicts and startup issues after feature > installations. > > --Pradeep > > > >> >> AmilaM. >> >> On Thu, Jan 31, 2013 at 10:24 PM, Pradeep Fernando <[email protected]>wrote: >> >>> Hi, >>> >>> Right now we are updating the P2-repo as and when an issue occurs. Can't >>> blame product teams/QA either since we are only doing smoke testing against >>> the p2-repo. >>> >>> >>> The idea is to incorporate feature installation in to integration tests >>> and sort out feature level issues early in the release cycle. There we >>> should test for most common user scenarios. >>> >>> eg: install IS feature set to ESB product and run both IS and ESB >>> integration tests. >>> >>> Can we use clarity to do the above ? >>> >>> Ideally this should be declarative. Means we should be able to give the, >>> >>> target platform : ESB >>> feature-list-to-install : <list of features> >>> integration test suite to run against the end product. >>> >>> may be im bit too ambitious. I'm ok to start the effort with whatever >>> implementation we have. >>> >>> Krishantha et al, WDYT ? >>> >>> >>> thanks, >>> --Pradeep >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Amila Maharachchi* >> Technical Lead >> Member, Management Committee - Cloud & Platform TG >> WSO2, Inc.; http://wso2.com >> >> Blog: http://maharachchi.blogspot.com >> Mobile: +94719371446 >> >> >> >> >> -- >> *Pradeep Fernando* >> Member, Management Committee - Platform & Cloud Technologies >> Senior Software Engineer;WSO2 Inc.; http://wso2.com >> >> blog: http://pradeepfernando.blogspot.com >> m: +94776603662 >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Dileepa Jayakody, > Software Engineer, WSO2 Inc. > Lean . Enterprise . Middleware > > Mobile : +94777-857616 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dharshana Warusavitharana Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : [email protected] <[email protected]> cell : +94772202595 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
