Blog

In my custom load testing class, we usually get into specific code examples that demonstrate how to do some tips and tricks in VUGen. One of the things I always like to bring up is the behavior or sprintf. This is a commonly used C function for string manipulation. Many a young LoadRunner lad has come across the dreaded memory violation error in their output log when using sprintf:
Error: C interpreter run time error: Action.c (10): Error — memory violation : Exception ACCESS_VIOLATION received.
Let’s look at why. Here is some code: Read Entire Entry

I was trying out the new Protocol Advisor in LoadRunner 9.5 this week, and I found it was not working as advertised. It wasn’t even recommending WEB as a protocol choice for recording a simple web script. Not good. The only thing it did recommend to me properly was RDP. If a person cannot figure out they are using RDP when they launch an RDP window, they probably should not be using LoadRunner. 🙂 I decided to dig a bit deeper and found I had discovered a bigger problem.

On my past several engagements, I had been using the client Read Entire Entry

This was developed as a result of load testing a bridal registry site written with BlueMartini. There needed to be a way for the Vuser to clean up its bridal registry at the end of each iteration. However, I couldn’t be assured of a specific number of items (because the item catalog changed frequently, and we varied the number of items added).

The web_submit_data function looks for a symbolic “LAST” to determine when it has reached the end of a variable argument list. This was modified by inserting it into a predefined argumen Read Entire Entry

// – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
// Brian Wilson – TechSouth, LLC
// – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

// – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
// xstrcat()
// more efficient version of strcat
// – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
char *xstrcat( char *dest, char *src )
{
while (*dest) dest++;
while (*dest++ = *src++);
return –dest;
}
/*char * xstrcat(char * dest, const char * src) // alternate version Read Entire Entry

This function (called EncodeText) may be a bit out of date, but can be used to replace special characters and use different encoding. You could put this in the very top of the vuser_init section of your script, or in the globals.h or other include file.
//——begin code—————
EncodeText(New,Orig)
char *New;
char *Orig;
{
int New_index;
int Orig_index;
int len;

len = strlen(Orig);
New_index = 0;
for (Orig_index=0;Orig_index<len;Orig_index++) {
Read Entire Entry

/*

This custom RTE function will auto generate a transaction timing
for every TE_wait_text. Paste this code into the top of your script,
or use as an include file.
Replace TE_wait_text with this function called TE_custom_wait_text
using the search and replace tool.

*/

int TE_custom_wait_text ( char * text, int timeout)
{
int rtnCode = 0;
char myTransName[24];
char spacelessText[24];
char * spacePointer;

memset ( spacelessText, ‘\0’, sizeof(spacelessText));

{
* spacePointer = ‘_’;
}

sprintf (myTransName, Read Entire Entry

From James Pulley:
———————-

I have never really cared for the use of the lr_user_data_point() and
having to pull up the user defined graphs for analysis. Instead I take
advantage of some undocumented functions

lr_set_transaction()
lr_get_transaction_duration()

I use these functions in tandem to determine if I need to create a custom tracking transaction where a transaction has run too long and is out of spec.

I can then compare raw numbers at the end of the test, a ratio of <transaction name>_out_of_spe Read Entire Entry

On my latest engagement, I needed a web script to go with all of the Citrix scripts I am creating. The web script was giving me some issues with correlation and NT authentication, so I decided to give Web Click and Script a try. I didn’t have much expectation since neither I nor my colleagues have been able to get it to work in the past, but I thought that it would be worth a try in 9.5. Imagine my surprise when it actually worked! This could partly be because the javascript is minimal. That seems to be where C&S hangs.

There i Read Entire Entry

Let’s say you are testing a web application and the service level agreement of response times for each web page is 1.5 seconds or below. You might want to automatically fail any transaction that comes back in a longer amount of time. You will need to measure the number of milliseconds in the transaction, and see exceeds this amount. You might need to set something like this up for any transaction where timing for milliseconds is crucial. Just because the business process passes, does not mean the transaction should pass, especially Read Entire Entry

I saw this on the LinkedIn.com discussion boards today. Someone was asking about troubleshooting Vugen 9.1 and 9.5 crashing when performing operations. Michael Weinstock of COLES IT in Melbourne, Australia responded:

If this is the same issue (and I suspect that is highly probable):

The root cause of this problem was identified as VUGEN referencing an incorrect version of ss32x25.ocx.

Our issue was addressed by a manual reregistration of this file as follows:
regsvr32 “c:\\windowssystem32ss32x25.ocx”
Do a search on affec Read Entire Entry