Next button is not getting clicked

[zar...@gmail.com]

Hi,

I’ve three page web application that I’ve recorded.  I used HTML protocol.

I’m able to save on the first page and click next, and the data on the second page is also saved but the next button is not getting clicked.

I’ve checked the headers, correlation is correct.  What else can I do?  Any help will be appreciated.

 

Thanks

[Anand Gattu]

Hey,

LoadRunner is not like your automation tools. Click on the "Next" button need not have to be recorded. Pls remember that, recording is happening on the network level, not on the screen level. As long as the data is captured by the script and same is send to the server, you are good to go...

Hope this helps

Regards

Kumar Gupta

Ishs Performance Testing Inst

--
You received this message because you are subscribed to the Google Groups "LoadRunner" group.
To unsubscribe from this group and stop receiving emails from it, send an email to LR-LoadRunner+unsubscribe@googlegroups.com.
To post to this group, send email to LR-Loa...@googlegroups.com.
Visit this group at https://groups.google.com/group/LR-LoadRunner.
To view this discussion on the web visit https://groups.google.com/d/msgid/LR-LoadRunner/b85c6891-18cc-411b-b4ba-480e2019106e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mital Majmundar]

How do you know it is not getting clicked? And are you concerned with "Button" being clicked or the proper page being loaded. Check if the desired page is being loaded. Put proper checks in place and also ensure you have correlated all the dynamic values. Also can you let us know what error you are getting because of which you are saying the button is not clicked?

 

Mital Majmundar

On Fri, Sep 8, 2017 at 11:29 PM, <zar...@gmail.com> wrote:

--

[James Pulley]

Perhaps you are running the wrong type of virtual user if you are insistent upon a button being pressed versus the request generated by the button being captured.   You have several options if you insist on an actual button press:

• GUI Virtual User
• TruClient Virtual User
• Citrix Virtual User
• Remote Dektop (RDP) Virtual User.

I, for one, do not believe that you need to run the full interface to generate the load.  This is a very 1996 and before way of looking at the load generation universe.   What you do likely need to do is have appropriate comments and transaction markers while you are recording so it makes it easier within your test script to find the URL which is being exercised as a part of the button press.   

You could always start a new recording session and then pause the actual recording until you arrive at the step for your button press.   Hit the record button, record the button press, stop recording.   The odds are significantly high that you will find a substantially similar patter of requests and responses in your existing test code.  This pattern would then represent the test traffic generated by the button press.

Don't be afraid to liberally use comments when you are recording as this will make it easier to identify key locations in your test code as well as the test data you typed in/selected versus what has been sent on your behalf