Hi all , As we discussed in the code review and the rest of the discussions, in order to make UI automation Friendly AppFactory we have noticed that there are some adjustments to do in automation and the AppFactory team as well. I would like to list down the points that we needed to accomplish for the above subject.
1. provide an API in order to get the life cycle stages and the check list status of the Life cycle management of an application. 2. Provide ID's in order to identify UI elements rather than Xpath Identification. Now in Life Cycle management we have hard coded the Life Cycle Stage of the application and checking against that hard coded value.But we came to a conclusion its better to have a Jaggery API in order to get the lice cycle stage of an application. Most of the time traversing the tables is done using a constructed Xpath and it is subject to change due to a minor modification of the page. Instead we propose to introduce ID's for the every possible UI element hence the changes to the Page Doesn't effect to the Page object model. IF appfactory team or automation team have further suggestions to this please reply to this thread. Thanks -- Randika Ratnayake, Mobile : +94773-440677 <[email protected]>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
