Testing: Load Profiles
Overview
Use this page to create and manage load profiles. A load profile is a saved configuration that defines how a group of simulated users connects to the system under test: which connection technology they use (such as Citrix Enhanced or RDP), how many users and agents to run, and which scenario and SUT profile to apply. It lets you model several distinct connection methods for the same environment without rebuilding a test from scratch for each one.
Before you load a profile into a run, its scenario must exist on Configuration: Testing: Scenarios and, if you want it to target a specific environment, its SUT profile must exist on Configuration: Systems Under Test: Profiles. Once a profile is defined here, you select it on Testing: Run Test to start a test, and its progress and history surface on Testing: Active Test and Testing: Test Runs.
This page lists every load profile grouped by technology, with each group showing a profile count and aggregate user and agent totals. From here you search for a profile by name, create a new one, and edit, rename, clone, or delete an existing profile directly from its row.
Key concepts
- Load profile - A saved configuration that defines how a group of simulated users connects to the system under test, including the connection technology, user count, and the scenario and SUT profile it runs. (related: Testing: Run Test)
- Technology - The connection method a load profile simulates, such as Citrix Enhanced, RDP, or Test Client. Profiles on this page are grouped by the technology they use.
- SUT profile - The System Under Test profile a load profile is linked to; it defines the target environment the load profile tests against. (related: Configuration: Systems Under Test: Profiles)
- Scenario - The sequence of actions simulated users perform once connected. A load profile runs the scenario it is linked to when a test starts. (related: Configuration: Testing: Scenarios)
When to use it
- You need a new way to simulate user connections (technology, user count, or linked scenario) before a test run.
- You want to confirm which SUT profile and scenario a specific load profile targets before scheduling it.
- You need to check the total simulated users and agents per connection technology before starting a run.
- You're renaming, cloning, or deleting a profile as test requirements change.
- You're searching for one profile among many across technologies.
Before you begin
- Decide the connection technology the new profile should use (Citrix Enhanced, RDP, or Test Client), since profiles are grouped by this choice.
- Create the scenario the profile will run, on Configuration: Testing: Scenarios, if the profile needs to execute a specific sequence of actions.
- Create the SUT profile the load profile will target, on Configuration: Systems Under Test: Profiles, if the profile needs to test against a specific environment.
- Confirm your account has the LoadProfilesEditor or GlobalAdmin role; without it, the New Profile button does not appear.
Common workflows
Create a new load profile
Persona: Load test operator
- Select New Profile in the page header.
- Expect: A dialog opens for defining a new load profile.
- Set the technology and name in the dialog, then select Create Load Profile.
- Expect: The dialog closes and the new profile appears as a row under its technology group, with that group's profile count increased by one.
- Type the profile's name into Search profiles to confirm it was saved.
- Expect: The table filters to rows whose name matches the typed text.
Verify: The new profile appears in its technology group under the name you gave it, and the page header's total profile count increases by one.
Clone an existing profile for a variant test
Persona: Load test operator
- Select the Clone icon on the row of the profile you want to copy.
- Expect: A new row is added to the same technology group with the same users, agents, and links as the source profile.
- Select Rename on the new row and enter a distinct name.
- Expect: The PROFILE NAME cell updates to the new name.
- Select Edit on the cloned profile to adjust its user count, agent assignment, SUT profile, or scenario.
- Expect: The profile's configuration opens for editing.
Verify: The technology group lists both the original and the cloned profile under distinct names, and the group's aggregate USERS/AGENTS totals reflect the sum of both.
Remove a profile that is no longer needed
Persona: Load test operator or admin
- Select the Delete icon on the profile's row.
- Expect: The Delete Load Profile confirmation dialog opens.
- Select Delete in the confirmation dialog.
- Expect: The dialog closes and the profile's row is removed from its technology group; the group's profile count and aggregate totals decrease accordingly.
Verify: The deleted profile's name no longer appears in any technology group, and the page header's total profile count decreases by one.
Steps
Step 1
Open the Load Profiles page.
Expected result: The page loads showing existing load profiles grouped under technology headers (Citrix Enhanced, RDP, Test Client), each row listing its USERS, AGENTS, SUT PROFILE, and SCENARIO values, with a header count of profiles across technologies.
This view is the starting point for reviewing, creating, or editing the load profiles a test run can use.
- The header reads 4 profiles across 4 technologies, though only three technology groups are visible until you scroll further down the page.
- Rows with no linked SUT profile or scenario show a dash in those columns.
-
Search profiles and Refresh are available immediately for filtering or reloading the list.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Search profiles | Filters the profile list to rows whose name contains the typed text; use it to locate a profile quickly when you manage many profiles across technologies. | free text | No | - |
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| PROFILE NAME | Identifies the load profile. | Shown as a clickable name in the accent color; selecting it opens the profile for editing. |
| ACTIVE | Shows whether the profile is active. | The only value captured is a green check mark, meaning the profile is active and available to select when starting a test; this capture does not show what an inactive profile looks like. |
| USERS | Shows the number of simulated users this profile runs when selected for a test. A higher count increases the simulated load the profile contributes; 0 means the profile currently generates no load. | Compare this value against the technology group's aggregate Users total to see each profile's share of the group's load. |
| AGENTS | Shows how many LoadGen agents are assigned to execute this profile's simulated users. At least one agent must be assigned before the profile can generate load in a run. | 0 means no agent is linked yet; the technology group's AGENTS total sums this column across its profiles. |
| SUT PROFILE | Shows which System Under Test profile this load profile targets. | A dash means no SUT profile is linked yet; a linked name appears as a clickable link in the accent color. |
| SCENARIO | Shows which scenario this load profile runs. | A dash means no scenario is linked yet; a linked scenario name opens that scenario's configuration page. |
| ACTIONS | Groups the row-level actions for the profile: edit, rename, clone, and delete. | Every row shows the same four icons regardless of the profile's state in this capture. |
Controls reference
Refresh
Reloads the load profile list and the per-technology user and agent totals from the server.
When to use: After a profile was changed elsewhere, or to confirm the counts shown are current.
Side effects: Read-only: re-reads existing data and does not change any profile.
New Profile
Opens a dialog for defining a new load profile.
When to use: When no existing profile covers the technology, user count, or scenario/SUT profile combination you need for an upcoming test.
Side effects: None by itself; opens a dialog, no profile is created until you confirm with Create Load Profile.
Create Load Profile
Submits the new-profile dialog and saves the profile.
When to use: After setting the new profile's technology, name, and any links in the dialog opened by New Profile.
Side effects: Mutating: adds a new row under the chosen technology group and increments that group's profile count and the page's total profile count.
Edit
Opens the profile's full configuration for editing.
When to use: When you need to change a profile's user count, agent assignment, or linked SUT profile or scenario.
Side effects: None until you save changes inside the edit view; saved changes update the profile's row values.
Rename
Opens a control to change only the profile's name.
When to use: When the current name no longer describes the profile's purpose but its configuration should stay the same.
Side effects: Mutating once confirmed: updates the PROFILE NAME cell for that row.
Clone
Creates a copy of the profile with the same technology, users, agents, and links.
When to use: When you want to reuse most of an existing profile's setup for a variant, such as a different user count, without rebuilding it.
Side effects: Mutating: adds a new row to the same technology group and increments that group's profile count.
Delete
Opens the Delete Load Profile confirmation dialog; selecting Delete again inside that dialog permanently removes the profile.
When to use: When a profile is no longer needed for any test.
Side effects: Mutating once confirmed: removes the row from its technology group and decrements that group's profile count and aggregate Users/Agents totals; selecting Cancel instead leaves the profile unchanged.
Cancel
Closes the Delete Load Profile confirmation dialog without removing the profile.
When to use: When you opened the delete confirmation by mistake or decide to keep the profile.
Side effects: None: no data changes.
Verify the result
When a new or edited load profile is saved, it appears as a row under its technology group with the name, active status, and USERS/AGENTS values you set, and the page header's total profile count updates accordingly. A profile intended to drive load in a test should show a non-zero USERS count, at least one agent in AGENTS, and real names (not a dash) in SUT PROFILE and SCENARIO if it needs to target an environment and run a specific flow. If a change you made does not appear, select Refresh to reload the list before assuming it failed. If a profile you expect to use in a test is missing from Testing: Run Test, check here first that it still exists.
Troubleshooting
- Symptom: A profile you just created or edited doesn't show its new values. Fix: Select Refresh to reload the list from the server before checking the profile again.
- Symptom: The New Profile button is not visible. Fix: Confirm your account has the LoadProfilesEditor or GlobalAdmin role; the button is hidden for accounts without it.
- Symptom: SUT PROFILE or SCENARIO shows a dash for a profile you need to run. Fix: Edit the profile and link a profile created on Configuration: Systems Under Test: Profiles or a scenario created on Configuration: Testing: Scenarios.
- Symptom: A profile shows 0 in USERS or AGENTS. Fix: Edit the profile to set a user count and assign at least one agent; a profile with 0 agents cannot generate load in a run.
- Symptom: You can't locate a specific profile among many rows. Fix: Type part of its name into Search profiles to filter the list.
- Symptom: You deleted the wrong profile. Fix: There is no undo after confirming in the Delete Load Profile dialog; recreate it with New Profile or use Clone on a similar profile and adjust it.
Related articles
- Next step: Testing: Run Test - Select a load profile here to start a test run.
- Prerequisite: Configuration: Testing: Scenarios - Create the scenario a load profile links to and runs.
- Prerequisite: Configuration: Systems Under Test: Profiles - Create the SUT profile a load profile targets.
- See also: Testing: Test Runs - Review past runs that used a given load profile.
- See also: Testing: Schedules - Schedule recurring runs that use a load profile.