Link for test plan - https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0Aiz7bX_8klOldDZCQ2tVMl84MnRIR1NhNGU3NDBKUEE&usp=sharing
Krishantha Samaraweera Senior Technical Lead - Test Automation. Mobile: +94 7777 599 18; blog: http://opensource-soa.blogspot.com/ WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. On Mon, Sep 16, 2013 at 8:24 PM, Krishantha Samaraweera <[email protected] > wrote: > Hi, > > I think we can use QA Test plan [1] to derive test cases for high level > scenarios listed. > > Thanks, > Krishantha. > > Krishantha Samaraweera > Senior Technical Lead - Test Automation. > Mobile: +94 7777 599 18; blog: http://opensource-soa.blogspot.com/ > WSO2, Inc.; http://wso2.com/ > lean . enterprise . middlewear. > > > On Mon, Sep 16, 2013 at 6:08 PM, Chamath Gunawardana <[email protected]>wrote: > >> >> >> >> On Fri, Sep 13, 2013 at 1:23 AM, Prabath Siriwardena <[email protected]>wrote: >> >>> Hi Chamath, >>> >>> I guess we need to review of the progress of integration test writing >>> weekly - in terms of code coverage.. That will help us find out where we >>> are and are we in a position to get 60% mark before mid Oct... >>> >>> Hi Prabath, >> >> Sorry for the delayed response. Currently the IS integration test >> coverage is standing at 16%. Will provide a weekly update. >> >> >>> Thanks & regards, >>> -Prabath >>> >>> >>> On Fri, Sep 6, 2013 at 10:34 AM, Chamath Gunawardana >>> <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> As we need to increase the integration test coverage of IS for the next >>>> release we need identify the priority areas/critical paths that we first >>>> need to be covered. Hence your input on this will greatly help. Please >>>> pitch in.. >>>> >>>> Please find below some resources and guidelines that you can get >>>> familiar with before we start writing the tests next week. >>>> >>>> * Krishantha and the Automation team have already written IS tests that >>>> we can refer to get started in [1]. >>>> * Please make your self familiar with automation framework and >>>> guidelines on writing tests in [2] if not already. >>>> * Use of the TestNG Annotations properly as Krishantha have mentioned >>>> in another mail thread since this will avoid simultaneous test runs which >>>> will cause tests to be fail. Also make sure you run the TestNG version >>>> 6.1.1. >>>> * Make server state consistent by cleaning the data after test. >>>> >>>> Also please find the IS integration test allocations in [3]. >>>> >>>> [1] - >>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/products/is/4.5.0/modules/integration/src/test/java/org/wso2/identity/integration/tests >>>> >>>> [2] - >>>> http://docs.wso2.org/display/TA100/Best+Practices+for+Writing+Integration+Tests >>>> >>>> [3] - >>>> https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AtS5Oii8ega9dEV4Qy05VVhoZ1Vkb2YzaHJWZGZJV3c#gid=1 >>>> >>>> >>>> >>>> Thanks, >>>> -- >>>> Best Regards, >>>> Chamath Gunawardana >>>> Technical Lead; WSO2 Inc. >>>> Mobile : +94776322240 >>>> >>> >>> >>> >>> -- >>> Thanks & Regards, >>> Prabath >>> >>> Mobile : +94 71 809 6732 >>> >>> http://blog.facilelogin.com >>> http://RampartFAQ.com >>> >> >> >> Thanks, >> -- >> Best Regards, >> Chamath Gunawardana >> Technical Lead; WSO2 Inc. >> Mobile : +94776322240 >> > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
