Testing: Load Profiles
Overview
Use this page to view and manage load profiles grouped by technology. A load profile defines how simulated users connect to a system under test using a specific technology, such as Citrix Enhanced, RDP, or Test Client, including how many users and LoadGen agents are assigned to generate that load. Grouping profiles by technology keeps connection methods separate, so you can see at a glance how many profiles exist and how much simulated load each one represents.
Before a profile is useful, you typically link it to a system-under-test profile that identifies the target environment and to a scenario that defines the test flow it executes; both show as a dash until configured. Once a profile is active and has users and agents assigned, you select it when starting a test run, which uses the profile's settings to simulate the configured load against the target environment.
On this page, you can search across all profiles, review each technology group's profile count and total users and agents, create a new profile, and edit, rename, clone, or delete existing ones directly from each row.
Key concepts
- Load profile - A configuration that defines how simulated users connect to a system under test using one specific technology, including how many users and LoadGen agents generate that load. (related: Testing: Run Test)
- Technology - The connection method a load profile simulates, such as Citrix Enhanced, RDP, or Test Client. Profiles are grouped by technology on this page, each with its own profile count and total users/agents.
- Scenario - The test flow a load profile runs when it is assigned one. A profile without a linked scenario shows a dash in the SCENARIO column instead of a link. (related: Configuration: Testing: Scenarios)
- SUT profile - The system-under-test profile identifying the target environment a load profile connects to. A profile without one shows a dash in the SUT PROFILE column. (related: Configuration: Systems Under Test: Profiles)
When to use it
- Before scheduling or running a load test, to confirm a load profile already exists for the technology and user count you need.
- To check how many simulated users and agents are allocated per profile across technologies at a glance.
- When you need to add a profile for a connection technology that isn't represented yet.
- When an existing profile needs updating: renaming it, cloning it for a similar setup, or deleting one that's obsolete.
- When you need to confirm whether a profile is already linked to a SUT profile and scenario before reusing it in a test.
Before you begin
- A system-under-test profile defined in Configuration: Systems Under Test: Profiles if you want to link the load profile to a target environment.
- A scenario created in Configuration: Testing: Scenarios if you want the load profile to run a defined test flow.
- The LoadProfilesEditor or GlobalAdmin permission to see New Profile, Edit, Rename, Clone, and Delete controls; without it these controls are hidden.
- At least one LoadGen agent available (configured under the relevant Configuration: LoadGen Agents page) to generate the load a profile defines.
Common workflows
Create a load profile for a new technology
Persona: Load-test admin
- Select New Profile.
- Expect: A new-profile form opens for choosing the technology and defining its settings.
- Choose the technology, set the number of simulated users, and select Create Load Profile.
- Expect: The form closes and the new profile appears under its matching technology group in the list, increasing that group's profile count and the page's total profile count.
Verify: The new profile's row shows the USERS value you entered, and the top summary line (for example '4 profiles across 4 technologies') increases by one.
Reuse an existing profile with Clone
Persona: Operator preparing a similar test
- Find the profile under its technology group and select the Clone icon in its ACTIONS column.
- Expect: A duplicate row appears in the same technology group with the same settings as the original.
- Select the duplicate's Edit icon, adjust the USERS or AGENTS value, and save.
- Expect: The duplicate's row updates to show the new USERS/AGENTS value, independent of the original profile.
Verify: Both the original and the cloned profile appear under the technology group with their own USERS/AGENTS values, and the group's total users/agents reflects both.
Steps
Step 1
Open Load Profiles.
Expected result: The page loads showing profiles grouped by technology, with Citrix Enhanced, RDP, and Test Client groups visible, each row's ACTIVE, USERS, AGENTS, SUT PROFILE, and SCENARIO values, and a summary reading '4 profiles across 4 technologies'.
This is the starting point for reviewing which load profiles already exist before running or scheduling a test.
- The Search profiles... field sits above the technology groups.
- Each technology group (for example Citrix Enhanced) shows a count badge and a right-aligned total of users and agents.
Step 2
Select Refresh.
Expected result: The list reloads: an unrelated Credentials expiring notification closes, the full header toolbar appears with Refresh and New Profile, and rows with a linked scenario now show an Open scenario icon in place of Rename.
Refreshing clears the transient notification overlay and confirms the current set of row actions and header controls before you create or edit a profile.
- New Profile is now visible in the header for creating another profile.
- A row linked to a scenario, such as Test: LoadGen Demo, shows Open scenario instead of Rename.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Search profiles... | Filters the technology groups and their rows to only load profiles whose name matches the text you type. Use it to find a specific profile quickly when many exist across technologies. | Free text | No | Empty (no filter applied) |
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| PROFILE NAME | Identifies the load profile by its display name. | The name is shown as a link; the text does not itself indicate status, only identity. |
| ACTIVE | Shows whether the profile is marked active. | A green checkmark means the profile is marked active; a gray x mark means it is marked inactive. An inactive profile can still have assigned users, agents, and a linked scenario, so treat this as a separate on/off flag rather than an indicator of whether a test is currently running. |
| USERS | Shows the number of simulated users this profile is configured to generate when run. | 0 means the profile is defined but has no simulated users assigned yet; a higher number is how many concurrent simulated users the profile drives when used in a test. |
| AGENTS | Shows how many LoadGen agents are assigned to generate this profile's load. | 0 means no agent is currently assigned, so the profile cannot generate load yet; each assigned agent runs a share of the profile's simulated users. |
| SUT PROFILE | Shows the system-under-test profile this load profile targets. | A dash means the profile has not been linked to a system-under-test profile yet; a name means tests run with this profile target that defined environment. |
| SCENARIO | Shows the test scenario this load profile is attached to. | A dash means no scenario is linked yet; a link means the profile runs that scenario, and you can open it directly from this row. |
| ACTIONS | Holds the per-row controls for managing the profile. | All rows show Edit, Clone, and Delete. Rows without a linked scenario also show Rename; rows with a linked scenario show Open scenario instead. |
Controls reference
Refresh
Reloads the load profile list from the server.
When to use: After creating, editing, or deleting a profile elsewhere, or when the group counts and totals look out of date.
Side effects: Read-only: re-fetches current data without changing any profile.
New Profile
Opens the form to create a new load profile.
When to use: When you need to define how simulated users connect for a technology that isn't yet represented, or add another profile for an existing technology.
Side effects: Mutating: once you select Create Load Profile in the form, the new profile appears under its technology group, increasing that group's profile count and the page's total profile count.
Edit
Opens the selected profile for editing.
When to use: When you need to change the profile's connection settings, assigned users or agents, or its SUT profile or scenario link.
Side effects: Mutating: saved changes update the row's USERS, AGENTS, SUT PROFILE, and SCENARIO values and the technology group's totals.
Rename
Lets you change the profile's display name in place.
When to use: When the profile's name no longer reflects its purpose, without changing its connection settings. Shown only on rows without a linked scenario.
Side effects: Mutating: updates the PROFILE NAME value shown in the list and wherever the profile is referenced.
Clone
Creates a copy of the profile with the same technology and settings.
When to use: When you need a near-identical profile, for example to test a different user count against the same technology.
Side effects: Mutating: adds a new row to the same technology group and increases that group's profile count.
Delete
Removes the load profile.
When to use: When a profile is obsolete and no longer needed for any test.
Side effects: Mutating: opens a confirmation dialog; confirming permanently removes the row and lowers the technology group's count and totals; Cancel closes the dialog without changes.
Open scenario
Navigates to the scenario linked in the SCENARIO column.
When to use: When you want to inspect or edit the scenario this profile runs, without searching for it separately. Shown only on rows with a linked scenario.
Side effects: Read-only: navigates away from this page; does not change the profile.
Verify the result
After refreshing or completing an action, the Load Profiles page shows each profile under its technology group with current ACTIVE, USERS, AGENTS, SUT PROFILE, and SCENARIO values, and the summary line (for example '4 profiles across 4 technologies') reflects the correct totals. A profile you just created, cloned, renamed, or deleted appears, updates, or disappears from its technology group right after you confirm the action. If a profile doesn't appear where expected, confirm you're looking under the correct technology group, since profiles are organized by technology rather than listed in one flat table. If the counts in a group header don't match the rows you can see, select Refresh to reload current data from the server.
Troubleshooting
- Symptom: A profile you just created with New Profile doesn't appear in its technology group. Fix: Select Refresh to reload the list; new rows and group totals only appear after refetching.
- Symptom: A row shows a dash in SUT PROFILE and SCENARIO. Fix: The profile hasn't been linked yet; use Edit to link it, or create the missing SUT profile or scenario first under Configuration: Systems Under Test: Profiles or Configuration: Testing: Scenarios.
- Symptom: USERS and AGENTS both show 0 even though ACTIVE shows a checkmark. Fix: The profile is active but has no simulated load assigned; open Edit to set a users and agents value before using it in a test.
- Symptom: New Profile or the row action icons (Edit, Clone, Delete) are missing. Fix: Your account lacks the LoadProfilesEditor or GlobalAdmin permission; ask an admin to grant it under Operations: Permissions.
- Symptom: The table shows 'No load profiles configured'. Fix: No profiles exist yet; select New Profile to create the first one for the technology you need.
- Symptom: A Credentials expiring banner covers part of the header toolbar. Fix: This is an unrelated system-wide notification, not part of this page; close it with the X, or reissue the token under Configuration: Credential Profiles.
Related articles
- Prerequisite: Configuration: Systems Under Test: Profiles - Load profiles link to a SUT profile that defines the target environment
- Prerequisite: Configuration: Testing: Scenarios - Load profiles link to a scenario that defines the test flow they run
- Next step: Testing: Run Test - A configured load profile is selected when starting a test run
- See also: Configuration: Credential Profiles - Resolves credential-expiry notifications shown on this page
- See also: Operations: Permissions - Controls who can create, edit, or delete load profiles here