Clincking Wrong Element

[Sebastian]

A while back Cody showed me how to fix a clicking step, so it will click the correct element.
I'm trying to Hover Over a roll down menu and click the first item on the list.
It never rolls down but I see the mouse doing something else. 
I think it is missing the element I'm after.
I think he went through the DOM to connect the step to the correct element.

[Anthony]

Hello Sebastian,

It sounds like you're after our "Mouse Hover" feature. This is done via the Elements Menu. This process will add the menu element to the Elements Explorer and insert a Mouse Hover step. Once positioned right before the step that clicks the first list item, your test should run as expected.

Here's a short video on how to do it.

Kind regards,
Anthony
the Telerik team

[Sebastian]

I've done this many times, the steps are recorded, they just don;t work correctly.

[Anthony]

Hello Sebastian,

OK, so you suspect the step is acting on the wrong element? You can use the "Locate in DOM" feature from the Elements Menu on the nearest element. Once in the DOM Explorer, locate the desired element and right click it. From the context menu you can:

1. Choose "Show Element Menu" and add a Mouse Action step.
2. Choose "Add to Project Elements", locate the element in the Elements Explorer, and use the new Step Builder feature to add an action step.

Regards,
Anthony
the Telerik team

[Sebastian]

When I try to acces the, "Show Ele,emt Menu", it is grayed out.
The element in the DOM is show with <> around it, is this just a heading?
It wont go any deeper from there.

[Sebastian]

Interesting update-

 

I decided to build a very small test to work with the roll down.

It works fine in my small test.  I copied the steps from the small test to the one I was having trouble with, now it won't work.  It must have something to do with the step preformed before the roll down.  The steps before must be causing the active area to change.  I do see it trying to click.  It clicks above on the browser itself and not in the window. I'm going to keep playing with it, any advise you can offer would be great.

[Anthony]

Hi Sebastian,

Unfortunately, without seeing the issue first-hand, I can only speculate as to what is happening. Is remote access possible for me to test this directly? If not we can resort to a GoToMeeting.

Regards,
Anthony
the Telerik team

[Sebastian]

A GoTo meeting is fine, let me know when.
Sebastian

[Anthony]

Hi Sebastian,

I've started a GoToMeeting now, please join if you are available. If not, please suggest a convenient time later this morning or after lunch.

1.  Please join my meeting.
https://www2.gotomeeting.com/join/983837074

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, call in using your telephone.

Canada: [phone]
France: [phone]
Germany: [phone]
Ireland: [phone]
Italy: [phone]
United Kingdom: [phone]
United States: [phone]

Access Code: 983-837-074
Audio PIN: Shown after joining the meeting

Meeting ID: 983-837-074

GoToMeeting®
Online Meetings Made Easy™

All the best,
Anthony
the Telerik team

[Anthony]

Hi Sebastian,

I found that two steps are causing the odd "out-of-browser" clicks:

261. Click 'ContentPlaceHolder1UcEditPQBBtnExportImage'
262. Handle 'Download' dialog.

When I disabled these steps, the subsequent clicks worked as expected and the test continued successfully. I am unclear why the download handling caused this issue, but I have passed it on to our developers to gain further insight.

On a side note, a test of this size (450 steps) is extremely difficult to work with and to maintain. It took me a considerable amount of time just to trim it down to a workable size where I could reproduce the issue quickly and reliably. As part of best practices, we highly recommend modularizing your project into smaller tests, and executing those tests as part of a test list. Testing an entire section of your application in one test is inherently fragile and difficult to maintain, as I'm sure you already realize.

We also recommend using Execution Delays and the "Continue on Failure" feature sparingly. Each action has a built-in "Wait on elements timeout", so an extra delay is often unnecessary (find the global setting under Quick Execution Options).

Also, I never saw errors on the "Connect to pop-up window" steps. I'm on version 2011.1.729 and using IE9.

Best wishes,
Anthony
the Telerik team

[Sebastian]

First off, thanks for all the help today.

I have to make large tests for some of things we do because they have to be done one after an other without re-logging in.  I use the continue on fails because many changes in text happen every week. I put waits all over due to lag times in the server that happen now and again.  I know about the new global wait, I'm just use to doing things the old way before that feature.

I'll probably go back and remove all the waits soon and just use the global wait.

I don't normally have any problems with long tests, I keep them under 500 steps as a personal rule.

 

[Anthony]

Hello Sebastian,

You're welcome. We have a "RecycleBrowser" setting on the "Web" tab of the "Edit Test List Settings" dialog which may be of interest to you. When checked, Test Studio will not close and reopen the browser between each test when executing the Test List. This is useful in cases like yours, where you need to keep the browser open (and stay logged in) between tests.

Regards,
Anthony
the Telerik team