On Fri, Sep 6, 2013 at 2:08 PM, Asela Pathberiya <[email protected]> wrote:
> > > > On Fri, Sep 6, 2013 at 12:20 PM, Chamath Gunawardana <[email protected]>wrote: > >> >> >> >> On Fri, Sep 6, 2013 at 12:07 PM, Krishantha Samaraweera < >> [email protected]> wrote: >> >>> Hi Chamath, >>> >>> Yes you are correct. XPaths can only be used if there is no other >>> choice. We have introduced Page object repository and mapper.properties [1] >>> file to hold all page elements separately. With this model, If there are >>> layout changes then changes to test case code will be minimal. However we >>> are still experimenting how to cater frequent UI changes with this >>> model. >>> >>> BTW, I can do a quick introductory session for you guys to start with BE >>> test automation. Let me know about team availability. >>> >>> This would be great Krishantha. Unfortunately we cannot have all the >> team members since the team is on a rotational leave. However today we have >> the starting members Asela and Pushpalanka also several others. Is it >> possible today? Also another session after 16th with remaining members? IS >> Team pls respond if you are able to make it today... >> >> Here is my +1 for today. >> > > +1, I guess most of them are here today and if not, we could let others > know. so we can have it today.. (around 4.00 PM). > > Great, we'll have it in 5th floor meeting room. > Thanks, > Asela. > > >> >> >> Thanks, >>> Krishantha. >>> >>> [1] >>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/platform-integration/test-automation-framework/4.2.0/org.wso2.carbon.automation.api/src/main/resources/mapper.properties >>> >>> >>> >>> >>> On Fri, Sep 6, 2013 at 11:39 AM, Chamath Gunawardana >>> <[email protected]>wrote: >>> >>>> >>>> >>>> >>>> On Fri, Sep 6, 2013 at 11:25 AM, Krishantha Samaraweera < >>>> [email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> The UI integration module has also been added to IS 4.5.0 [1], you >>>>> will find some test cases which can be used as a reference for starting UI >>>>> scenarios. >>>>> >>>>> Let's focus on UI integration tests only if we cannot write BE test >>>>> cases. IMO, we can start writing UI tests once we achieve good coverage >>>>> though BE tests. And after finalizing with user and management views which >>>>> is going to be a new feature in next release. >>>>> >>>>> Thanks Krishantha for the updates. Agree with you on first writing the >>>> BE integration tests. >>>> Also when writing UI tests we need to define the "Id" attribute for UI >>>> elements as and when required without using Xpaths in the tests. Since if >>>> we use Xpaths the test gets depend on the layout which will break if the >>>> layout changed. >>>> >>>> Thanks, >>>>> Krishantha. >>>>> >>>>> [1] >>>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/products/is/4.5.0/modules/integration/tests-ui/ >>>>> >>>>> >>>>> >>>>> >>>>> On Fri, Sep 6, 2013 at 10:46 AM, Johann Nallathamby >>>>> <[email protected]>wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> This webinar [1] also might help to get a high level idea of our >>>>>> automation framework. >>>>>> >>>>>> [1] >>>>>> http://wso2.com/library/webinars/2013/04/wso2-test-automation-framework-approach-adoption >>>>>> >>>>>> Thanks, >>>>>> Johann. >>>>>> >>>>>> >>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Best Regards, >>>> Chamath Gunawardana >>>> Technical Lead; WSO2 Inc. >>>> Mobile : +94776322240 >>>> >>> >>> >> >> >> -- >> Best Regards, >> Chamath Gunawardana >> Technical Lead; WSO2 Inc. >> Mobile : +94776322240 >> > > > > -- > Thanks & Regards, > Asela > > ATL > Mobile : +94 777 625 933 > -- Best Regards, Chamath Gunawardana Technical Lead; WSO2 Inc. Mobile : +94776322240
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
