In the domain of performance testing, a 'workload' is a key term that signifies the collection of tasks and processes that a system or application is subjected to during the testing process. LoadGen, a leading performance testing tool, adopts a structured approach to defining workloads. Here, we delve into the process of defining workloads within LoadGen, focusing on the core components: Flow/Workload, Usertype, Application, Application Blocks, and Actions.
- Flow / Workload: The Flow, also known as the Workload, forms the backbone of the testing process. It represents the sequence of actions that simulated users will undertake during the test. It's the main item that encapsulates everything that will happen in a given test scenario, from the applications that will be used to the types of users that will be simulated.
- Usertype: The Usertype serves as a placeholder to define specific sets of users who will run a particular application. The Usertype can be determined based on a percentage of total test users, specific test usernames, or those defined in the LoadGen Director active canvas (test users). Notably, definitions in the LoadGen Director supersede the others. This enables a more granified control over the distribution of user types in the testing process.
- (LoadGen) Application: This is the specific application you want to test. In the context of web testing, it's the placeholder for testing a specific site or test case. You must choose the specific browser you want to test with and can add multiple applications (therefore, multiple different browsers in one usertype). Furthermore, you can override the proxy settings on an application as well. These LoadGen applications are interchangeable, providing flexibility in how you structure your testing scenarios.
- Application Blocks: Application blocks are used to split applications into manageable sections for better debugging. These blocks are often used for different actions such as starting an application, entering text, or saving a document. Application blocks can also be used for defining essential measurements you want to take, such as the time it takes to load a program, a webpage, or open a specific file. This division into blocks facilitates a more structured and organized approach to testing.
- Actions: Actions represent the specific tasks that the simulated users will perform during the test. They aim to replicate real user interactions with the system, providing an accurate picture of how the system will perform under realistic conditions.
Understanding these components is crucial for creating effective and meaningful workloads in LoadGen. By carefully defining and structuring these elements, testers can create a variety of testing scenarios that provide in-depth insights into the performance and reliability of their systems or applications under different conditions. The resulting data can then be used to identify and address potential issues, ensuring that the system or application is ready for real-world deployment.
- To create a new test flow for an untested application;
- To create a different test flow for a tested application;
- To create new test flows for the first time.
- When the LoadGen Studio has opened, click New at the top of the window in the ribbon
- This will open a new window: the LoadGen Studio - Flow Wizard.
LoadGen Studio - Flow Wizard Part 1
- Enter the name of how you want to call this flow (your test script).
- You can also add a description to clarify what you wish to test in this flow (optional),
click Next when finished.
- In the next step, you can add User Types (these User Types can have separate applications to test), the default setting is Normal and this will add all of you test users ( this is most applicable in LoadGen Load & Performance Testing).
- By clicking on the dropdown button next to Select a predefined set you can change your User Types. You are able to customize to your own design (it is also possible to add user types in existing flows).
- Leave usertypes on Normal and click on Next.
- In this step, you can add the Applications you want to add to your Flow (what applications you want to use for your test).
LoadGen Studio Application wizard
- A new window will open: LoadGen Studio Application wizard.
- Enter the name of the application and provide an (optional) description.
- Select an Icon and click on Next.
- The following step is to add Blocks to your application (to split your application into smaller and more manageable sections) e.g. starting the application, closing the application, writing text, opening the document, or saving the document.
We split applications into manageable blocks (sections) for better debugging. Best Practice is to use blocks for different actions e.g. starting an application, entering text, or saving a document. It can also be used for defining essential measurements you want to take, e.g. how long it takes to load a program, load a webpage, or open a specific file.
- Click on Add.
- A new window will pop up, please enter how you want to call this new Block and add a (optional) description.
Add predefined blocks from LoadGen: When you click on the dropdown button next to add Add you can select predefined blocks from LoadGen, e.g. Starting/Closing application.
- Add blocks to start the application, do an action, and close the application (you are able to add and remove blocks in the Studio main form), when ready click on Next.
- You will now see a summary of your created application, with name, description, blocks, and for what usertypes. Click on Save to continue.
Actions and Validations need to be added in LoadGen Studio Recorder
LoadGen Studio - Flow Wizard Part 2
- After saving the flow you will return to the LoadGen Studio - Flow wizard, you will see your created Application here. You can add as many applications as you wish here. Click Next when you have added all the applications you want in this test (you can add/remove applications in the LoadGen Studio Main form).
- The next step in the wizard leads you to add Variables; this can be e.g. a file location or e-mail address, etc. Standard LoadGen adds LastValidationX and LastValidationY; these variables are needed for your validations. (this is explained in Article LoadGen Validations).
- Click Next to continue.
- You can now determine how many times you want the flow to repeat your defined Applications. For first-time setup, we recommend you keep it at 1. Click Next.
- You will now see an overview of your Flows configuration, including usertypes, applications, variables, and iteration settings. Click Finish to save your flow and open your new Flow in the LoadGen Studio.
- Once completed you will see the following overview of your Flow in the LoadGen Studio.