I thought the whole idea of launch pages didn’t make it past the millenium?
Archive for the ‘Articles’ Category
LoadRunner not accepting cookies on HTTP 302 redirect
Posted on May 25th 2010 by Joel Deutscher
I recently came across a problem with trying to record a login to a website. After posting my login credentials, I received a 302 redirect that contained several Authentication cookies. Unfortunately, LoadRunner was not recognising the cookies and the subsequent page redirected me back to the login page.
As login was obviously working in the browser, I recorded a clean session using the fabulous Firebug. Now that I was able to directly compare the HTTP headers. It quickly became evident that the reason was that LoadRunner wasn’t reading the entire 302 Header. Time to pull out Firebug.
Continue Reading…
LoadRunner Analysis Tips and Tricks
Posted on February 25th 2010 by Joel Deutscher
I was looking to put together a list of LoadRunner Analysis reporting tips and tricks for our company Wiki. It didn’t take long however to find a comprehensive list by Nick Wilton.
I highly recommend taking a look at this list, and I have highlighted my top 5 tips below. To read the rest of Nick’s tips, or to leave him a thank you message, check out the full article over at JDS Australia here.
Using Regular Expressions in LoadRunner
Posted on February 10th 2010 by Joel Deutscher
It has previously been identified how to enable Regular Expressions in LoadRunner. A big thanks to Charlie, Tim for getting this working, and Dmitry for proposing the challenge.
In this post, I am to going demonstrate a practical use of bolting the regular expression engine ontop of LoadRunner. After all, it is more effort than LB/RB. So why go to all the trouble? Hopefully the following example will demonstrate a scenario where regular expressions can be invaluable.
Continue Reading…
Execute the 100% Load Test First
Posted on January 11th 2010 by Joel Deutscher
There has always been something about performance testing that has bugged me over the years. It’s the standard approach of ramping up the amount of load on each test execution cycle.
The typical order of executions for a performance test is:
- Smoke Test
- 25% Load
- 50% Load
- 75% Load
- 100% Load
The flaw, as I see it, lies in the order of execution. I think we an improve on this concept by aiming to ramp down instead. Continue Reading…
