Hi Dimuthu, With this approach, everyone who wants to test Jaggery apps will have to write the same Java code by extending your base class, which is redundant. Hence, IMO, the best options would be to wrap your base class and write a maven plugin. So, what other's will have to do is, just add that configuration in the pom and tests will be executed automatically without writing any Java code.
/Ruchira On Mon, Jul 7, 2014 at 3:39 PM, Dimuthu De Lanerolle <[email protected]> wrote: > Hi, > > I have started working on this. Our plan is to write a common test class > inside carbon-platform-integration-utils module which product teams can > extend and start running jaggery tests residing inside > [PRODUCT_HOME]/repository/deployment/server/jaggeryapps/xxx/test directory. > Invocation of each test endpoint will be treated as a separate test case > resulting number of test cases to be executed will get equal to number of > test endpoints to be invoked. > > Regards > > Dimuthu De Lanerolle > Software Engineer > WSO2 Inc. > lean . enterprise . middlewear. > http://wso2.com/ > Tel. : +94 11 2145345 Fax : +94 11 2145300 email : [email protected] > > -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com>* *email: [email protected] <[email protected]>, blog: ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, mobile: +94 77 5493444*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
