Browser based automation

[manivannan_r]

Hi All, I had faced some issues while automating Browser based applications It was new for me and I am not able to proceed further on that Scenario: 1. Initially I launched the application and started to spy the full main screen and then I proceeded across sub pages(i.e. 1,2,3 and soon) further then the process flow is like I will have to come back to the main page in reverse order to perform other tasks (i.e. 3,2,1 and soon) what happened here is a big surprise for me is that the link in application modular when I spied for the first cycle started to change when I am back to the same screen for the next time so I was under a situation to re-spy the screen which were spied initially. Please suggest me a solution for this and thanks in Advance.

[Anonymous]

Hi Raja, You have to take these Link as dynamic and for which you need to supply the Dynamic value of this Attribute, you can do that via GET PARENT URL or with some calculations from which you can derive the Dynamic URL.

[shahariar_k_bhu]

You could try to disable the parent_url attribute, in most cases I've been able to identify the elements without using that attribute.

[manivannan_r]

@ avi2kaushik currently I am working on using the dynamic values fed into the URL but still wen I am repeating it for the next time not able to get to a conclusion on which value to feed dynamically again

[John__Carter]

I think what Avani means is that the URL of the page is not constant. Often web apps append session data to the URL, eg http://somewebpage.aspx?sessionid=1234. If you keep the Parent URL attribute ticked in Application Modeller then the element will only be found for this URL, and when the page is revisited and the URL changes to http://somewebpage.aspx?sessionid=5678, the element will not be found.Resolution: untick the attribute.

[manivannan_r]

Thanks John and avi2kaushik for your solutions! Hi John, agreed But I keep all the attributes unchecked which change dynamically and then keep only one attribute checked ie. Path and make it dynamic and pass input values to them at run time and still the & value in them is getting changed always this was the problem which was happening here.

[Denis__Dennehy]

I would always recommend having at least one identifier attribute ticked as well as the Path - just to validate the path is for the correct element if the underlying appliction has changed in some way. Also, for some dynamic web sites the Path cannot be used at all because it is changable. The browser automation guide discusses this possibility.

[manivannan_r]

Hi Dennis, I will try keeping any one attribute checked and the path as well. Thanks