Loadmance
Search…
⌃K

Terminology

Terms that will come in handy when performing performance testing
Assertion: Assertions are undeniably valuable, providing the criteria you set to determine whether the a will be considered a “pass.” You can use them to run against a sample and its subsamples to ensure returned values match expected results.
Concurrency: A measure of the number of simultaneous or parallel threads of execution.
Dedicated IP: It refers to private IP addresses that you can use in your tests.
Delay Thread Creation Until Needed: If this option is checked, the ramp-up delay and startup delay are performed before the thread data is created. If not checked, all the data required for the threads is created before starting the execution of a test.
Delimiter: A comma is the default delimiter, but if your file uses tabs, enter \t here.
Duration: Time set for testing.
Engine Count: The number of devices that will work for the test.
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.
Loop Count: It is 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.
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
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.
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.
Test Pass Criteria: Decision rules used to determine whether a test item has passed or failed.
Think time: The amount of time required by a user to determine and execute the next action in a sequence of actions
Thread Group: This Thread group is the most basic thread group. It has some standard settings and it can be adapted to fit most load test scenarios.
Throughput: Throughput is the number of request that are 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.
Variable names: Define your column name mapping as a list of comma-separated strings. BlazeMeter uses these names as parameter names to refer to data columns. To skip a column, add an extra comma with no name.
Virtual User: A simulation of the activities that would be performed by a user according to the operational profile