LoadRunner supports the widest range of enterprise environments and is the only performance testing product to be customized and certified to work with ERP/CRM applications from PeopleSoft, Oracle, SAP, and Siebel.
I code HTML to create a web page that I can link to in my status reports.
So that transaction names are listed in the sequence of manual steps, I assign transaction names such as "T00_Login","T01_Homepage" etc.).
I capture the image of each screen into an MS-Word file for documentation purpose.
As needed, I note for each screen/step its testability status (such as not available for use, script having errors, is being ignored, data parameterization, variations in values, etc.)
I prefer not to use the default location, but to store all files associated with a script together in the same folder. Unfortunately, this means that if I switch between different tests, I have to remember to change the default settings every time.
When you open VuGen for the first time, click the box on the lower left corner so that you can select existing scripts.
The first step to creating a new script is to select single or multi-protocol.
Before working with Java protocols, make sure you have the JDK in the PATH environment variable. Otherwise you'll get this message:
When selecting a Java protocol:
When you open a new script, the name of the script is, by default, noname1. The name of the next new script is automatically incremented to noname2, etc.
The default Working Directory for v7 scripts is C:\Program Files\Mercury Interactive\Mercury LoadRunner\bin\
But rather than starting from scratch, I prefer to open an existing script and "Save As" the new script name. This allows me to modify a script file that has features I know works.
Sooner or later, you're going to wish you had a prior version of a script you're working on. To make sure you have a version to fall back to, zip up the script folder immediately after you get a script to work.
I prefer recording into an action (such as one named "Recording") that I have deleted from the Runtime Settings' Logic section. After the default Action section is deleted, it still appears in the list at the top of the icon list, but is shown with a grayed out icon. New actions are inserted beneath it. I do this to avoid accidentally running recorded scripts before editing, which I've done too many times because new actions are automatically added to the Logic list in Runtime Settings.
Before recording, write down the manual actions. Give a unique identifier to each step.
As you record, insert each identifier from your list after each action.
Record several actions in sequence (rather recording one action, then stopping and starting with another action). This allows you to recognize sequence numbering (in applications such as PeopleSoft) that you need to correlate in your script.
Immediately after recording, copy the "Generation Log" to a text file in a different folder than the script you are working on. The next time you record, it will be wiped out. You'll need the file to see exactly what went to and back from the server.
Every time a change is made in a script, that script needs to be recompiled.
