Hi all, While designing the test framework, its good if we can keep in mind that jaggery2 product also underway. Any thoughts?
Regards, UdaraR On Thu, Nov 14, 2013 at 10:15 AM, Madhuka Udantha <madh...@wso2.com> wrote: > Hi Krishantha and test automation team, > > I would like to get your opinion on this task regard to > > is there standard methodology on current testing framework where we can > added such testing framework or better to go on fully independent model? > > > My thinking is, > > - As it is application level testing frame work, better to work with > much independent of the current system > - Where application writer (developer) can run test for specific > application rather running all test for platform or product > - It will help to maintain both test framework with low cost > - Each test frame have it's own scope (such as > platform/product/appilcation). if not, complexity of the code and system > will be increase but there will be API interface for interaction among > the > test framework. > - And I thought to have interface (simple REST interface) in jaggery > test frame work where current test framework also can interact with it into > some extend. > > Thanks > > > On Tue, Nov 12, 2013 at 5:57 PM, Madhuka Udantha <madh...@wso2.com> wrote: > >> Hi, >> >> >> Still we do not have jaggery test framework even though there are >> considerable jaggery applications were developed. It is not easy maintain >> those jaggery applications/APIs steady without testing frame work. >> >> >> Now onward we will starting $subject as it is important for jaggery as >> well as there is no JS testing framework under WSO2 Platform. Testing >> framework will be under application level such as mocha, jasmine. Test >> frame will be apply to (basically)test. >> >> >> >> - jaggery API (js functions and arguments ) >> - REST APIs that are expose under jaggery application >> - With test coverage reporting >> >> >> We will be evaluating existing JavaScript test frame works regard >> mocha[1], jasmine[2], Qunit[3], Vows[4], expresso[5], nodeunit[6] and >> jsunit[7] to $subject. >> >> >> >> All suggestions are welcome. >> >> >> [1] http://visionmedia.github.io/mocha/ >> >> [2] http://pivotal.github.io/jasmine/ >> >> [3] http://qunitjs.com/ >> >> [4] http://vowsjs.org/ >> >> [5] http://visionmedia.github.io/expresso/ >> >> [6] https://github.com/caolan/nodeunit >> >> [7] https://github.com/pivotal/jsunit >> >> >> >> Thanks >> -- >> *Madhuka* Udantha >> Senior Software Engineer >> Development Technologies >> WSO2 Inc. : http://wso2.com >> >> *Mobile*: +94774066336 >> *Blog*: http://madhukaudantha.blogspot.com/ >> > > > > -- > *Madhuka* Udantha > Senior Software Engineer > Development Technologies > WSO2 Inc. : http://wso2.com > > *Mobile*: +94774066336 > *Blog*: http://madhukaudantha.blogspot.com/ > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog : http://udarakr.blogspot.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
