Web step failed
i'm using load runner 6.5 to do the load test for our product. When I replay the script, it's giving me a error as "web step failed,Either form not found or the data does not match to the form".
I know that the problem is coz of paricular form is having data dependency. So, i must use passing parameter for dependent field. But the real problem is,
The program is developed using hidden form fields, so i can't able to see in which URL it's particularly generating the key. Without knowing that how can i pass the parameter. Is there any function to get the information about the URL. and also i want to say that the dynamic value is generated in the "NAME" field of action not in the "VALUE" field.
I recorded in the context sensitive mode, i know that in context sensitive mode , no need to pass the parameter, It'll automatically refer the previous value from cache. But still i'm facing this problem.
I hope somebody can help me.
Re: Web step failed
We're having the same problem when load testing our Web Application (Apache / Servlet based Java app) but our application logs are indicating sessions (ie. mapping on to a single user) are timing out about the same as we get the "data does not match to the form" error.
Did you manage to resolve your problem? I believe it may be Load Runner not managing sessions properly on the web server rather than an application problem.
Re: Web step failed
This is a problem common to web applications. In order to manage state, they require that the client submit some sort of dynamic session ID, that has already been suppied by the application.
This requires the implementation of what Mercury calls dynamic data correlation. You can capture and save dynamic data (even from hidden fields) by use of the web_create_html_param(_ex) functions or the web_reg_save_param function, and use the captured data when you send future web requests.
The trick with these functions is you have to insert them in the script *before* the call that receives the session ID from the server.
To find the dynamic data (and ultimately, where you should insert your web_reg_save_param function), you should record the same script twice, and compare them. The use of extended logging is also very helpful here.
BTW, recording in context sensitive mode is not a sliver bullet to solving this problem. I prefer to record and play back in analog mode, because I have more control of what requests I'm sending to the server.
Once you capture the dynamic data, and save it as a LR parameter, you can use it just like any LoadRunner parameter