On Fri, Sep 6, 2013 at 11:25 AM, Krishantha Samaraweera <krishan...@wso2.com > 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 <joh...@wso2.com>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 >> <chama...@wso2.com>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
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
