Cannot view replay response time in vugen

150 views
Skip to first unread message

gurpreet kaur

unread,
Mar 7, 2014, 2:49:07 AM3/7/14
to LR-Loa...@googlegroups.com
Hi All,

I am using Vugen version 11.00 Patch 4. I am scripting web url using web(http/html).
I am not able to view replay response time in Vugen.
Please tell me the reason.

Thanks in advance.

Regards,
Gurpreet

James Pulley

unread,
Mar 9, 2014, 9:38:26 PM3/9/14
to LR-Loa...@googlegroups.com

You haven’t inserted and transaction (lr_start…lr_end…) transaction markers, which is how you would have generated timing statements in a VUGEN execution log.   That whole mess of auto transactions by step and action only occurs when you get into the controller.   Odds are you have missed a whole class of requirements on page and critical event timings that were not defined as you recorded the script.

 

What happens often in parallel to this is not setting expected conditions on each step during recording (nor branching of code when the expected result does not occur).   Take a critical look at your code and your requirements and make certain that you are not missing whole classes of data and work

--
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-LoadRunne...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

gurpreet kaur

unread,
Mar 10, 2014, 12:28:07 AM3/10/14
to LR-Loa...@googlegroups.com, james....@jamespulley.com
Hi James,

I have inserted lr_start_transaction and lr_end_transaction and m using ie9 but still i am not able to view the replay response times. Have done it numerous times on different URLS but Vugen is not generating response times for all the URLS.

James Pulley

unread,
Mar 10, 2014, 9:48:17 AM3/10/14
to LR-Loa...@googlegroups.com, james....@jamespulley.com
(1) Create a new script, any C-based virtual user type will do.

(2) Place this code in the main iterated section of your virtual user

   lr_start_transaction("Foo_PASS");
   sleep(2100);
   lr_end_transaction("Foo_PASS", LR_PASS);

   lr_start_transaction("Foo_FAIL");
   sleep(1100);
   lr_end_transaction("Foo_FAIL", LR_FAIL);

(3) Make sure the log is turned on in the run time settings

(4) Run 15 times

(5) Look at the output window

If this works in the new virtual user, what does this tell you about your virtual user?   If this does not work in another virtual user what does this tell you about your installation of the tools?

When examining a problem, it is often advantageous to look at the problem pattern in it's simplest form to allow you to understand the scope/size of the problem.
Reply all
Reply to author
Forward
0 new messages