Thanks you for your help to get me accepted to the GSOC 2014. thanks and regards.
On Thu, Mar 20, 2014 at 2:17 PM, Malintha Adikari <[email protected]> wrote: > Hi Rukshan, > > > On Thu, Mar 20, 2014 at 1:23 PM, Rukshan Chathuranga < > [email protected]> wrote: > >> Hi all, >> >> for this architecture what i planed to do is create generic test >> script file from the define BDD scenario by language processing. >> > > Yes, This file should be in standard formatted file (ex: xml...) and your > language processing component should be able to convert it back to natural > language. ( Idea is to store test cases in this standard format and users > can retrive those test cases as natural language test scenarios). > >> After that, mapped the appropriate command and attribute of the command >> to the appropriate wso2 TAF services as steps. >> > > No. You have to build a component that convert the processed test > scenarios (ex: xml....) in to test scripts mapping with the common API. > There are two tasks here > > 1. Design a Common API that exposes backend services of products > 2.Component that convert your processed scripts (xml) to test scripts. > > >> Then test scripts are generated as normal test cases. then let TAF to or >> Using Common API it is possible to run the test cases. >> >> Generated test scripts should be executed with WSO2 Test automation > Framework. > > >> This is what is supposed to do for the GSOC. So if their anything i >> missed in the proposal please let me know. >> >> > Thanks and regards. >> >> >> On Mon, Mar 17, 2014 at 10:26 AM, Malintha Adikari <[email protected]>wrote: >> >>> Hi Rukshan, >>> >>> Yes, You have to implement the Common API depending only on TAF. TAF >>> provides clients for back-end admin services. Consider about simple >>> scenario and try to understand the requirement. Think about single backend >>> admin service and think TAF provides client for that. Map that single >>> scenario with the test writers end. That would help you to complete the >>> architectural design. Also try to finalize tools.APIs you are going to user >>> for each stage. >>> >>> Regards, >>> Malintha Adikari >>> >>> >>> On Sun, Mar 16, 2014 at 9:26 AM, Rukshan Chathuranga < >>> [email protected]> wrote: >>> >>>> Thanks Dharshana, >>>> >>>> Does Common API only Depends on the WSO2 TAF? Since This Tool >>>> is going to Deploy inside the TAF no need to Communicate with other >>>> Services right? Because TAF care about other Back end Services. >>>> >>>> Is that mean common API have to map keywords only to the TAF functions >>>> and services? >>>> >>>> Thanks and regards. >>>> >>>> >>>> On Sat, Mar 15, 2014 at 2:09 PM, Dharshana Warusavitharana < >>>> [email protected]> wrote: >>>> >>>>> Hi Rukshan, >>>>> >>>>> The idea of the common API is basically a common interface which will >>>>> communicate with the all available Automation Framework modules. >>>>> IeAutomation Framework Engine, And Admin services and other supporting >>>>> modules in Framework side. >>>>> >>>>> As you can see in the diagram there is basically two modules, one >>>>> which will convert the keyword based tes.t script to common formatand >>>>> next module is which will trigger the test depending on the resources >>>>> available in the Automation framework. >>>>> >>>>> Thank you, >>>>> Dharshana. >>>>> >>>>> >>>>> >>>>> On Sat, Mar 15, 2014 at 10:46 AM, Rukshan Chathuranga < >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> This Question is related to this diagram. >>>>>> >>>>>> >>>>>> http://rukspot.com/sites/default/files/images/wso2/wso2_Test_Archi_2.png >>>>>> >>>>>> >>>>>> 1. function of the Test Execution Engine would be run the Keyword >>>>>> driven testing. >>>>>> >>>>>> 2. Function of the common API would be mapping keyword to the >>>>>> backed services. >>>>>> 3. Thus we need to use Robot framework for implement Keyword >>>>>> driven automation instead of JBeahve. >>>>>> >>>>>> >>>>>> So what would be the correctness of this thoughts? >>>>>> >>>>>> Thanks and regards. >>>>>> >>>>>> -- >>>>>> Department Of Computer Science & Engineering, >>>>>> Faculty Of Engineering, >>>>>> University Of Moratuwa. >>>>>> Sri lanka. >>>>>> WEB: http://rukspot.com/ >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Dharshana Warusavitharana >>>>> Senior Software Engineer , Test Automation >>>>> WSO2 Inc. http://wso2.com >>>>> email : [email protected] <[email protected]> >>>>> Tel : +94 11 214 5345 >>>>> Fax :+94 11 2145300 >>>>> cell : +94772202595 >>>>> blog : http://dharshanaw.blogspot.com >>>>> >>>>> lean . enterprise . middleware >>>>> >>>> >>>> >>>> >>>> -- >>>> Department Of Computer Science & Engineering, >>>> Faculty Of Engineering, >>>> University Of Moratuwa. >>>> Sri lanka. >>>> WEB: http://rukspot.com/ >>>> >>>> >>> >>> >>> -- >>> *Malintha Adikari* >>> Software Engineer >>> WSO2 Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> mobile: +94 71 2312958 >>> Blog: http://malinthas.blogspot.com >>> >> >> >> >> -- >> Department Of Computer Science & Engineering, >> Faculty Of Engineering, >> University Of Moratuwa. >> Sri lanka. >> WEB: http://rukspot.com/ >> >> > > > -- > *Malintha Adikari* > Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > Mobile: +94 71 2312958 > Blog: http://malinthas.blogspot.com > Page: http://about.me/malintha > -- Department Of Computer Science & Engineering, Faculty Of Engineering, University Of Moratuwa. Sri lanka. WEB: http://rukspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
