Automating a sent email using gmail.

[Doug]

I am attempting to automate the process of logging into gmail and sending an email out.  I am able to write a test with correct steps, but they are not working all of the time because gmail seems to have a dynamic id assignment.  The trouble I am having is after clicking compose, the "send to" field find logic is id=:8t, tagname=TextArea.  Other times the "send to" field is id=:86, tagname=TextArea, other times id=:92.  The results are, sometimes the test will work perfect and send the email, but other times it won't be able to find the "Send to" element after the "click compose email" step.

Do you have any suggestions as to how I should change the find logic on the "Send To" "Subject" and "Field" Elements of a composing email on gmail so that I can get a consistent element find?

[Mario]

Hello Doug,

Thank you for contacting Telerik Support.

When working with a scenario containing dynamic id's, we must take advantage of other properties which are unique to these elements. In the particular case of using Gmail I found the 'To' (textarea),  'Subject' (input) and 'Message Body' (div) fields could be located uniquely using the following properties respectively:

tagname=textarea
name=to
aria-label=Address

tagname=input
name=subjectbox
aria-label=Subject

tagname=div
role=textbox
aria-label=Message Body

If you set the corresponding find logic filters for the properties above, the To',  'Subject' and 'Message Body' fields should be found uniquely on each playback.

Let me know whether the suggestion helps.

Regards,
Mario
Telerik

[Doug]

Thanks a lot.

I was able to find use this logic to find them.  I did have another, find logic working, but this is definitely cleaner.

I am having another issue however, I am trying to highlight all of the emails in the inbox and delete them.  I am successfully able to find the "highlight" all button checkbox, and the delete button using the find logic:

tagname = div
role = button
aria-label = Delete

However, the click command does not appear to actually click the button and carry through the delete action.  While watching the test, it appears the delete button gets highlighted when the delete click step comes up, but there is no action.   If I manually click the button during execution, it works fine.

Is there some sort of harder click I can employ than the click command?  You know, something that will automate clicking the mouse with 10 lbs of pressure instead of the normal 5lbs.  Just kidding, but you get the point.

[Mario]

Hello Doug,

Glad to hear my suggestion was useful to you.

As for your issue with the delete button, try enabling the 'SimulateRealClick' property of this click step. If you were writing your script in code, enabling the property would be analogous to using the MouseClick() method to literally move the mouse and make a real click on the element as opposed to the Click() method which is considered a 'DOM-click'.

Let me know if it helps.

Regards,
Mario
Telerik

[Doug]

Thanks a lot, that worked perfect.

I don't know why I hadn't thought of that before.