4 Answers, 1 is accepted
0
Hello Nut,
Thank you for the shared details.
Please let me know if you have tried to enable 'SimulateRealTyping' for this 'Enter text' step (see the screenshot)? Does this keep the text in the Input field?
In case the issue still persists, I will appreciate if you can send me the sample test and allow me access to the application under test. Is this possible?
Regards,
Elena Tsvetkova
Progress Telerik
Thank you for the shared details.
Please let me know if you have tried to enable 'SimulateRealTyping' for this 'Enter text' step (see the screenshot)? Does this keep the text in the Input field?
In case the issue still persists, I will appreciate if you can send me the sample test and allow me access to the application under test. Is this possible?
Regards,
Elena Tsvetkova
Progress Telerik
0
chanut
Top achievements
Rank 1
Rank 1
answered on 30 Oct 2018, 02:41 AM
Thanks Elena, I will test as your recommend.
0
chanut
Top achievements
Rank 1
Rank 1
answered on 30 Oct 2018, 10:30 AM
Hi Elena,
Good news, I can run script as your recommend.
However, I have another issue about checkbox object. Telerik cannot run script of this object after capture finish.
Please see those steps via attach files.
0
Hi Nut,
I'm glad to hear that your initial problem is fixed.
About the second issue you face, it is completely different. From the attachment you sent us with execution log, it seems the problem is that the checkbox element find logic is recorded with dynamic ID. This means that each time you record such element it has one ID and upon second run of your application it generates completely new ID. This is how your application works.
For such cases, what you have to do is 2 things: first, try changing the find logic priority during recording, so that next time you start recording, you will not have the new dynamic ID element recorded by id, but by some other logic (name, tagindex, xpath, etc.). If this does not work (sometimes applications are written with not enough unique attributes to work with them), you can manually change the find logic of such elements using the Find Expression Builder for that purpose.
Here is an article describing how you can do implement the above suggestions. Please try them out and let me know how it worked.
Best Regards,
Daniel Djambov
Progress Telerik
I'm glad to hear that your initial problem is fixed.
About the second issue you face, it is completely different. From the attachment you sent us with execution log, it seems the problem is that the checkbox element find logic is recorded with dynamic ID. This means that each time you record such element it has one ID and upon second run of your application it generates completely new ID. This is how your application works.
For such cases, what you have to do is 2 things: first, try changing the find logic priority during recording, so that next time you start recording, you will not have the new dynamic ID element recorded by id, but by some other logic (name, tagindex, xpath, etc.). If this does not work (sometimes applications are written with not enough unique attributes to work with them), you can manually change the find logic of such elements using the Find Expression Builder for that purpose.
Here is an article describing how you can do implement the above suggestions. Please try them out and let me know how it worked.
Best Regards,
Daniel Djambov
Progress Telerik