Core Performance Testing Principle:
Script
Overview
The details of creating an executable performance test are extremely tool-specific. Regardless of the tool that you are using, creating a performance test typically involves scripting a single usage scenario, then enhancing that scenario and combining it with other scenarios to ultimately represent a complete workload model.
Load generation tools are inevitably behind evolving technologies and practices. Tool creators can only build in support for the most prominent technologies, and, even then, these have to become prominent before the support can be built. This often means that some of the biggest challenges a performance testing project faces may include: getting your first three-user, two-scenario, three-loop prototype test implemented with no script errors, parameterized variables, authentication and sessions handled correctly, data collected correctly, and users generally being simulated in such a way that the application under test cannot legitimately tell the difference between real users and simulated users. Plan for this and do not be surprised when it takes significantly longer than expected to get it all working smoothly.
Learn more through PerfTestPlus Training
This topic is covered in the following PTP training courses:
- Scott Barber´s Performance Testing Software Systems: A Heuristic Approach
- Scott Barber's Principles Of Performance Testing (Designed for Managers and Executives)
- Scott Barber´s Performance Testing Software Systems: An Introduction
- Scott Barber's Performance Testing Software Systems; Applied (Using client's tool of choice)
Content adapted from:
by: J.D. Meier, Scott Barber, Carlos Farre, Prashant Bansode, and Dennis Rea