Skip navigation.

Mercury LoadRunner

LoadRunner Certification

Mercury LoadRunner | performance testing
I looked through the new LoadRunner certifications.

Accredited Integration Specialist in HP Performance Center v9. Two Prometric exams, $150 each.

Accredited Systems Engineer in HP Performance Center v9. Two exams, look somewhat similar to what Mercury had before, $750 each.

Rights to Run LoadRunner

Mercury LoadRunner | performance testing | performance testing tools
Where the myth that you can use LoadRunner with a regular user came from? I got a client who refused to give me admin rights and I should research this question again. I did it before – but, in my practice, I usually return to the same question after such period of time that the only thing I remember about it is that I researched it before.

Well, it took some time. Doesn't look like the new Mercury knowledgebase is a major search improvement.

Simulating Remote User Experience

Mercury LoadRunner | performance testing | performance testing tools
Remote user experience may differ significantly from the experience of users using local network. It is not a new thing for web developers, but often missed by developers of corporate applications. Many clients have remote offices with limited bandwidth and high latency that may cause performance problems. If it is a concern, there are ways to verify remote user experience. If we speak about LoadRunner it is possible to mention the following ways to simulate remote/WAN users:

HP to Drop Mercury Name

functional testing | Mercury LoadRunner | non-functional testing | performance testing | performance testing tools
From the note in SD Times: "Russell Daniels, vice president and CTO of HP Software, told SD Times that HP believes its brand is stronger than Mercury Interactive's, and thus all of Mercury's products will carry the HP tag." Hm... Depends in what area... Well, can't say that the trend eliminates concerns about Mercury's merge with HP.

HP to buy Mercury Interactive

general software testing | Mercury LoadRunner | performance testing | performance testing tools | test automation | test management tools | test tools
On Tuesday 7/25/2006, CNNMoney.com (along with *many* others) broke the news that the rumored HP/Mercury deal is really happening. A summary and my reaction is below. See the entire release here and draw your own conclusions.
July 26 2006: 9:22 AM EDT
NEW YORK (Reuters) -- Hewlett-Packard agreed on Tuesday to buy Mercury Interactive for about $4.5 billion in stock, or $52 per share, in a bid to expand the computer maker's business software operations.

Performance Bottlenecks / Diagnostics

Mercury LoadRunner | performance testing | performance testing tools | Rational Performance Tester | stress testing | Visual Studio Team System 2005
Another great article by Scott Barber Diagnosing Symptoms of Poor System Performance (see pp.14-20) continues to discuss practical approaches to diagnose problems. Together with the previous Scott’s article about the subject How to Identify the Usual Performance Suspects (see pp.20-29) it is a must reading for everyone testing performance.

Mercury NYC Local User Group

functional test tools | GUI test tools | Mercury LoadRunner | performance testing tools | Visual Studio Team System 2005
On Tuesday I attended Mercury NYC Local User Group. There were two presentations from Mercury – product update and business process testing. Most people were interested in functional testing.

Some things that were interesting for me:
- Mercury plans integration with the new VisualStudio, no details
- New TestDirector (for Quality Center 8.2) is re-written to J2EE, multiplatform now
- Quality Center 8.2 includes Actuate reports

LoadRunner and the GPL license: MI a potential victim to Stallmanism?

Mercury LoadRunner
[textile]

Saturday afternoon, I spent listening to the monthly SPIN lecture here at Pune. The speaker was *Prakash Khot*, a senior architect from *CA* (Hyderabad). The topic was the *Eclipse TPTP* (Hyades) project and open source in general.

One of the more interesting things Prakash mentioned was that CA consciously does not use GNU/products covered by the GPL copyleft license, preferring instead, their home-baked TOSL. What then are the implications for Mercury LoadRunner, which is based on the GNU *LCC*, GNU *Regex* engine and the GNU *GCPP*?