Why sometimes WebUi record correctly steps and other times not

Nice thread... thanks Karla.

Support, I ran into same situation almost every week. after I recorded new step when I compare old step and new steps find logic, both are same. Somehow new step works fine.

I see this one most of the time on selection of a ComboBox item.

Note: I got confirmation from my Development team there is no changes on particular items.

Waiting for solution.

Thanks,
Madhu.  

Hello Karla,

I'm not sure what you mean exactly when you say "a release or promotion is executed on the application." Presumably the application has somehow changed and steps recorded through Test Studio beforehand are now failing.

An element must be found before an action or verification can be performed on it. The element's Find Settings determine what attributes to use and how to find it. If one of the attributes used in the Find Settings changes in the app, then the element cannot be found and you'll get an error. This is expected behavior. Here is a troubleshooting guide on how to resolve that error. Here is more info on best practices in this area.

@Madhu
If you're certain the Find Logic is the same between steps, and nothing changed in your app, we'll need to see the issue first-hand to diagnose it. Please provide more information.

All the best,
Anthony
the Telerik team

Hi,

Thanks Anthony for the response, but what I'm trying to explain was similar that Madhu  explain here too.

For example the application that I'm using change in some section that do not implicate the Test Case to run.  But not sure why sometime steps recorded look like lost the information, so they do not find which button or field have to click. So, I need to record again the step to make that this

Also, I talked to developers to see if the name of items change on the code, but when I receive the answer that they do not change anything related with my test cases, not sure why I need to record again the steps.

sometimes the steps are recorded with the same name in WebUi, and sometimes just add a "0" or "1" at the end (like a new item on the step). And After I do this, the steps work.

Then, in the attachments you can see what I'm trying to explain in my first example, about the Print button.
I had recorded the steps to click on Print button, and was found by WebUi. The image of the page, is from WebUi story board. But not sure why, when I put the test to run, then on this step fail, and the print button is not found!
I had recorded, and looks like WebUi found the element. I recorded this step many times and not sure why is not read during the run.

Thanks,

Hello Karla,

It sounds like something dynamic is rendering at run-time, such as a URL query or Frame ID. This could explain the behavior you're describing, even if the elements themselves remain unchanged. If your app uses frames, see the bottom of this page for troubleshooting tips. If your app renders pages with a dynamic URL portion, such as query, consider changing the Elements Page Compare Mode in Project Settings > Recording Options.

Again, without more information there's no way to determine why that step fails. The Export Result to File feature from the Step Failure Details is the best way to send us that information. If you feel that information is sensitive, attach the resulting .zip file to a support ticket, which is confidential unlike this forum.

Regards,
Anthony
the Telerik team

Hi again,

Looks like this is a similar issue like the one I reported in this ticket:
http://www.telerik.com/automated-testing-tools/community/forums/test-studio/general-discussions/issues-recording-rad-tree-view-and-rad-buttons.aspx

The issue reported before was resolved bu itself when I updated WebUi.

But with the actual issue, not sure if this is because I record to click on Print Button from a child window. I mean, I'm on a page, I flip the page, to select another option and then enter to other page and on this second window I have issues to run correctly the step recorded.

Hello Karla,

I must reiterate that without more information there's no way to determine why that step fails. Please use the Export Result to File feature I previously mentioned so we can gain a better insight into your issue.

Ideally we'd like to reproduce the issue locally to troubleshoot it. Can you provide us a copy of your test and access to your application? If not, does a public site exhibit the same behavior?

Kind regards,
Anthony
the Telerik team

Well, looks like the issue with the Print button is fixed by itself. I didn't do anything on the Webui, neither on the steps, just I recorded again this step this week, and looks like the element was recorded with other name, and now when test is running, the step is read correctly, and simulates the click on that button.