Add Hover step without having to re-record?

[Donna]

I already have my elements in the element explorer and I would like to add a Hover step to one of them, similar to how I can use the Step Suggestions to add a Click step (BTW, I really like the Step Suggestions feature) without having to re-record.

Can I do this for a Hover?

Thank you for your time and assistance.

Donna

[Alan]

I don't believe so, but I'll wait for an Admin to fully answer.  If you have a lot of elements to hover over, one thing you could try is to re-record the hover over one of the elements, copy and paste that step wherever you need it, and change the Primary Target in the Properties window for those steps.

[Boyan Boev]

Hi Donna,

Step Suggestions provides actions/verifications over the properties/events of the elements.

Mouse hover is a desktop command. That means that it affects the browser in the same way that a real user would affect the browser. 

To add a mouse hover action to an existing element you have 2 options.

- Edit the element in the Element Explorer and add the action in the browser.

- Add a simple coded step: 

element.MouseHover();

I recorded a short video as a demonstration of both options.

Let me know if this helps.

All the best,
Boyan Boev
the Telerik team

[David]

This one vexes me too...

If the desktop command is not relative to anything on the screen, I don't understand why desktop commands can't be in the suggestion list.  When I look at one of my hovers, for example, the coordinates are 0,0 relative to the center of the element - the position of the element is calculated at run-time (or so it would seem).

Is there something on the live page that is captured behind the scenes?

[Boyan Boev]

Hello Donna,

The actions in the Step Suggestions come from Test Studio Translators therefore every action is related to that concrete element.

I filed a future request to implement this functionality. You can track its progress and vote for it here: Public URL.

Thanks for your input, which we rely upon to improve our product.

Kind regards,

Boyan Boev
the Telerik team

[Donna]

This worked perfectly for my needs! Thank you so much for the idea. I was specifically trying to avoid re-recording or having to write a coded step and this did it.

I noticed, however, in doing this, that the procedure was a memory hog. I had to Save my work, close Test Studio, then re-open it and continue working (I had quite a few I needed to do) after re-targeting the Primary target a few times. But that was a minor work-around for a solution that worked for me.

Donna

[Donna]

Thank you for submitting this for a future request. Now that I've discovered Step Suggestions I prefer working with the already-saved elements and the suggestions (instead of re-recording) and I was disappointed to discover that the Mouse actions were not available. Thanks.

[Alan]

DITTO big time on the memory hog issue.  We are excited for R1 in 2013 that addresses memory issues!