Scipts are failing in edge browser

Hello Pranavi,

In the shared execution log files I noticed the find expression of the element, which cannot be located on the page, uses TagIndex. This said, I suspect this could be leading to the differences between both browsers. 

In order to check if this is indeed the case, I would recommend you to modify the find expression of that element by removing the TagIndex - you could include TagName instead. Possibly the ID of the element might be sufficient to identify the element but this depends on the application structure. Once you change that, please execute the test and double check if this will work as expected. 

If the issue still persists, you can turn on the annotations (please see point 5. in this article) and execute the test against Edge again. With this, you will be able to see which is the target element highlighted for that step. Can you please also share that with us?

Additionally, please let me know if you can share a sample test with us and if the application can be reached outside your network. I ask this, because it will be easier for us if we can reproduce the issue on our end in order to see what might be going wrong.

Thank you for your cooperation in advance. 

Regards,
Elena Tsvetkova
Progress Telerik

Hello Elena,

 I have tried as you guide me. that is element find expression changed by tag name but it is not working.

here a providing sample scripts zip file. those are original scripts that means in that changed by tag name is not implemented.please guide me based on the sample scripts.

Note: please execute those scripts in BizNext Sample Product Company.(to change company go to left panel ->company menu in that double click on company name.

 

 

Hi Pranavi,

Firstly, I would like to thank you for the provided additional information and sample tests. I have reviewed the steps in detail. Unfortunately I was not able to execute the two tests because they both start with a step which tries to run a "GLogin" test that was not included in the archive provided by you.

Nevertheless, I was able to reproduce a similar problem with Edge which is triggered only by Desktop command: Left Click steps (DesktopActionDescriptor). I could not find any steps of this type in the two tests provided by you and therefore I am not sure this is the same issue that you are experiencing. Still, I have created a public feedback about it, which you can follow on this link.

Meanwhile, I would suggest you to uncheck the "SimulateRealClick" property of the "Click" steps in the problematic tests and try executing them again. Please bear in mind that this change could be dangerous because it will force the steps to only trigger the "click" JavaScript event. All other JavaScript events required by the internal logic of your application should be triggered manually with "Invoke JavaScript Event" steps. You can find them in the "JavaScript Events" Section of the Step Builder.

Additionally, in case the workaround is not applicable for your environment, we would need the "GLogin" test  in order to continue the investigation of the problem.
 
Please let me know if you need any further assistance.

Regards,
Konstantin Adamu
Progress Telerik