Description : Discussion on Components Test Framework Date: Tue Jul 20-2010
Attendees: Samisa, Sumedha, Azeez, Chamara Silva, Suho *Discussion action points:* Use descriptive property names as axis2server, axis2client and carbon.home Comment out the default values in the framework.properties file and add then as default values for getProperty() Make the variables in ServerLogin Class private Using template and command patterns when writing the test framework Each tests should be tested 1. with out login 2. with login 3, with logout (this is to check whether each admin service logs out properly) Use descriptive class names as TestRunner and TestFrameworkSettings Adding logs entries all the test cases Suho On 1 July 2010 10:59, Chamara Silva <[email protected]> wrote: > For a time been we are using separate pom to run test framework.please > refer 1.png for get brief idea. we have two options of using admin > service stub.option one is test framework can use generated admin > service stub after build each of the component. or we can use admin > service wsdl from the component source and generate stub from test > framework pom.(please refer attached images). > > Thank you, > Regards, > Chamara > > On Wed, Jun 30, 2010 at 5:21 PM, Hiranya Jayathilaka <[email protected]> > wrote: > > > > > > On Wed, Jun 30, 2010 at 5:07 PM, Suhothayan Sriskandarajah < > [email protected]> > > wrote: > >> > >> Description : Discussion on Components Test Framework > >> > >> Date: Wed Jun 30-2010 > >> > >> Attendees: Samisa, Sumedha, Prabath, Milinda, Chamara Silva, Suho > >> > >> Discussion action points: > >> > >> The Components Test Framework(CTF) should be able to test any WSO2 > Carbon > >> based products > >> > >> The stubs for the Admin Services should not be created at run time but > >> rather they have to be added as jars > >> > >> There should be two different phases in the Test Framework > >> 1. configurations > >> 2. testing > >> > >> The current sequential testing structure should be changed and > >> The CTF should be able to get its configuration and testing information > >> from one or more config files and run the tests accordingly. > >> > >> The structure of the Config file to be decided ( .xml .property or etc ) > >> > >> The testing code for each module should be situated in the SVN location > of > >> the Component's source code as > >> [PacchageName].test > > > > Does this mean we are going to merge this code into the carbon trunk > itself? > > Thanks, > > Hiranya > > > >> > >> Suho > >> > > > > > > > > -- > > Hiranya Jayathilaka > > Senior Software Engineer; > > WSO2 Inc.; http://wso2.org > > E-mail: [email protected]; Mobile: +94 77 633 3491 > > Blog: http://techfeast-hiranya.blogspot.com > > > > > > -- > Suminda Chamara Silva > Senior Software Engineer - QA > WSO2 Inc. > Mobile: +94 718 302858 > blog: http://chamaras.blogspot.com >
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
