I made a recording that goes to a website, fills in a login name, tabs to the password and clicks on submit.
Has been working for a couple of weeks with no issues. I created a second recording that has an additional
step, but also working without issue.
PROBLEM:
We are running the latest version of WPM.
With no changes to the web page, server or recording... both recordings stopped working. Walking through each action in the first step...
I notice that the problem seems to be a failure to recognize the SUBMIT button. Both recordings fail at the same spot.
TROUBLESHOOTING:
1. I was able to walk through all the actions by manually going to the website directly.
2. I walked through each action of each step for both transactions, and both fail on the same action.
How can the recording change on its own?
The element is obviously there... and I am able to press submit when the error window is cleared.
Has anyone seen this in their environment?
UPDATE (2 hours later):
Digging deeper into the code of the website I found an innocuous change in the code right before the recording failed.
It begs the question... what exactly is recorded and used to let WPM know it is seeing the same element?
3/6/2014 -- 9:56 AM
<asp:Button ID="LoginButton" runat="server" CssClass="button" Text="Submit"
OnClick="LoginButton_Click" />
Recording is working here...
3/6/2014 -- 12:29 PM
<asp:Button ID="LoginButton" runat="server" name="submit" CssClass="button" Text="Submit" UseSubmitBehavior="false"
OnClientClick="submitClick(this)" OnClick="LoginButton_Click" />
Recording stops working...
I am thinking this was probably the reason for failure... but would like to know from WPM developers what is actually recorded?
What... from the example above was the major difference causing the element to not be recognized?