Calendar

August 2006
S M T W T F S
« Jul   Sep »
 12345
6789101112
13141516171819
20212223242526
2728293031  

Categories

I’m known to be wrong occasionally…

In my earlier post about Planets, I stated that it looked as though our solar system would gain three additional planets. I guess I spoke too soon. Apparently, scientists have agreed to demote Pluto to the status of “dwarf planet” thus removing it from the canon of recognized planetoids. Oh yeah… and the other three I mentioned (Ceres, Charon, and Xena)… not planets. (cry)

Let’s pour one out for our fallen celestial comrade…

August 25th, 2006 | Category: Science | Leave a comment

QTP License Needs

According to Mercury support, when executing QTP scripts with LoadRunner, you onlyneed an installation of the QTP tool and any required add-ins on the load generating machine. You will not need the license for the tool, as the GUI VUser licenses within the LoadRunner Generator will be used as the license for the tool.

August 25th, 2006 | Category: LoadRunner, QuickTest Pro | Leave a comment

LoadRunner Limitations with QuickTest Pro scripts

According to my discussions with Mercury’s Technical Support, there are several limitations that LoadRunner has when executing QuickTest Pro scripts. Apparently, your QTP Scripts cannot:

  • access external files.
  • use external libraries.
  • have reusable actions.
  • use shared libraries.
  • reference reusable actions in other scripts.

The general rule of thumb that the tech support agent suggested was to ensure that you have all referenced code inside the script directory. This is to ensure that LoadRunner passes everything required of the test to each Load Generating machine.

August 25th, 2006 | Category: LoadRunner, Quality Assurance, QuickTest Pro | Leave a comment

Performance Testing with LoadRunner using QuickTest Pro

I have spent some considerable time on the phone with Mercury Tech Support regarding performance testing a Java Swing application. One approach we have successfully proven was utilizing QuickTest Pro to exercise our application while generated load through LoadRunner.

Here are some important details that I have gleaned:

  • It will be necessary to obtain GUI VUser licenses for the LoadRunner Controller to execute the scripts.
  • You will need to install QuickTest Pro (and necessary plugins) on each machine needed to exercise the application.
  • Your QTP scripts will need to implement transations around each business process to capture timing data.
  • Services.StartTransaction “Name”
  • Services.EndTransaction “Name”
  • Each machine needed will also need to the LoadRunner Agent installed and running for connectivity.

    •  This is some preliminary information. I will post more as I learn it.

    Edit:

    I also learned that load generating machines need to have the following application installed in order for the LoadRunner Controller to communicate and execute the QTP scripts on a destination machine. You must have the application under test (AUT) installed or accessible, an installation of QuickTest Pro (an required plug ins), and the LoadRunner Agent Process installed and running.

    In cases of having multiple terminal Services sessions, you must have the LoadRunner Agent Process running on each session and refer to each session as a seperate Load Generating machine in the controller. I believe you reference each instance as MachineName:0, MachineName:1, etc. Please correct me, if I am wrong here.

    August 25th, 2006 | Category: LoadRunner, QuickTest Pro | One comment