Terminology
Assertion: Assertions are undeniably valuable, providing the criteria you set to determine whether a test will be considered a "pass." You can use them to run against a sample and its subsamples to ensure returned values match expected results.
Active Engines: The number of test engines currently running and available for test execution.
AVG RT (Average Response Time): The average time taken for requests to receive responses during a test run, measured in milliseconds.
Concurrency: A measure of the number of simultaneous or parallel threads of execution.
Current Agent: Shows the number of active agents compared to total available agents for test execution.
Dedicated IP: Private IP addresses that you can use in your tests for consistent source addressing, especially useful for applications with IP whitelisting.
Engine Count: The number of devices that will work for the test.
Expiration Date: The date when your current subscription plan expires.
Geolocation: The geographic location from which your test traffic originates, configurable in both Cloud and Private modes.
HealthCheck: A separate product offering within the Loadmance platform for monitoring application health.
IP Access Control: Security feature that restricts platform access to specific IP addresses or CIDR ranges.
Iteration: Iteration defines the complete journey of a user mentioned in the test case. It is a group of transactions which denotes the end-to-end flow of the user action.
KPI (Key Performance Indicators): KPIs are metrics that enable measuring our results and success, according to parameters we choose to be relevant and important.
Last Check Result: The outcome of the most recent verification of your test configuration.
Loop Count: The number of executions for the script. For example, if the loop count is 2 and number of threads is 100 then the script will run 200 times. If the loop count is set "forever" then new threads will keep starting until the tests are stopped.
Max Concurrent Users: The maximum number of simultaneous virtual users allowed under your subscription plan.
Max Test Duration: The maximum time allowed for a single test run based on your subscription plan.
Max User Count: The peak number of concurrent users during a test execution.
Monitor Count: The number of monitoring points available in your HealthCheck subscription.
Number Of Threads: It represents the total number of virtual users performing the test script execution.
Performance Test Script: A simulation of user or component activity that contributes to the load on the system under test.
Private Engines: Test engines running on your own infrastructure that can be managed through the Loadmance platform.
Public IP/Private IP: The external and internal network addresses of your test engines.
Ramp-Up: The act of increasing the load on a system in a measurable and controlled way. For example, if you have 100 users with a ramp-up period of 50 seconds, JMeter will take 50 seconds to get all 100 threads running, adding 2 threads per second.
Register Command: The Docker command used to register a new private engine with the Loadmance platform.
Request IP: Button to contact Loadmance support for purchasing dedicated IP addresses.
Required Engines: The number of test engines needed to execute your planned test.
Sampler: Samplers tell JMeter to send requests to a server and wait for a response. They are processed in the order they appear in the tree.
Scheduler: This schedules the tests. You can set custom duration and startup delay to create the threads in this section.
Status Badges: Visual indicators showing project metrics that can be embedded in external websites or documentation.
Test Notifications: Alerts about test creation, updates, execution, and results.
Test Pass Criteria: Decision rules used to determine whether a test item has passed or failed.
Thread Group: The most basic thread group. It has some standard settings and it can be adapted to fit most load test scenarios.
Throughput: The number of requests processed per time unit (seconds, minutes, hours) by the server. This time is calculated from the start of first sample to the end of the last sample. Larger throughput is better.
Total Engines: The complete count of test engines available in your private infrastructure.
Total Test Count: The number of test executions included in your subscription plan.
Variable names: Define your column name mapping as a list of comma-separated strings. Loadmance uses these names as parameter names to refer to data columns. To skip a column, add an extra comma with no name.
Virtual User (VU): A simulation of the activities that would be performed by a user according to the operational profile.
VU per Engine: The number of virtual users each test engine can simulate during test execution.
Last updated