Loadrunner Standards

This piece presents a standardized framework for LoadRunner performance testing, drawing from training materials developed by Starbase, a performance testing specialist. The guide emphasizes consistency across the entire testing workflow.

Abbreviation System

The framework uses coded abbreviations:

• aa - application names
• nn - unique user identifiers
• vv - version numbers
• ss - sequence numbers

This creates concise, trackable naming throughout projects.

Virtual User Naming

Rather than descriptive names causing confusion, users are identified simply (for example, “abcd01”). Supporting documentation in spreadsheets or databases describes actual functionality, maintaining simplicity while preserving clarity.

Script Organization

Action files follow the pattern: virtual user identifier plus business process description. Steps are labeled with user ID, sequence number, and action type. Transactions capture the business actions being timed, maintaining consistency across performance metrics.

Directory Structure

A hierarchical folder system organizes all testing materials:

Project/
├── Documentation/
├── Results/
├── Scenarios/
└── Virtual Users/
    ├── Development/
    ├── Live/
    └── Vanilla/

This architecture facilitates team collaboration and presents professional reporting to stakeholders.

Change Control Lifecycle

Scripts progress through defined stages:

1. Initial vanilla recording - Raw captured scripts
2. Development enhancements - Version increments during enhancement
3. Live deployment - Production-ready scripts
4. Redevelopment cycles - Each with designated locations

This ensures clear version tracking throughout the project lifecycle.

Benefits

This standardized approach introduces consistency, quality, version control and efficiency across performance testing initiatives.