Run a test#
To run tests, the user needs to have the Run permission. The users with the Team owner and Manage users permissions manage access. For more information, see Permissions.
To run a test, use one of the following methods:
Click Run test immediately after creating or editing it.
On the Tests page, click
for the required test, go to the Load profile tab and click Run test.
The test will run after some time.
Note
If there are no available resources, the current test will be queued.
View test details#
The running test is displayed in the Test runs in progress pane of the Test Runs page:
To follow the testing click Test Details. The page opens that contains:
Test run settings. Type of load, a comment section, and total test run duration:
Current stats. Average test run scores for the last 10 seconds:
Throughput. Total requests per second and Errors per second plotted against Running VUsers.
Response Time. 95% response time of all requests plotted against Running VUsers. See transaction breakdown in Detailed stats.
Anomaly detection#
An anomaly is a large deviation of key metrics from the average in a moving window during the test. Anomaly detection allows you to see non-standard behaviour of a system under test online and simplifies the analysis of metrics at the end of the test.
PFLB Platform analyzes response times for the entire test and individual transactions using AI model and detects anomalies:
Response Time deviation is extreme response time deviation from average values in a sliding window.
VUser and Response Time inverse correlation is the inverse correlation of response time as the number of virtual users changes. For example, response time decreases significantly as the number of virtual users increases.
To enable anomaly detection, follow these steps:
In the upper-right corner of the window, click
. The dialog opens:
Click the Detect anomalies within a test toggle.
Set up the anomalies detection sensitivity for your test.
Note
Using an AI model does not exclude the detection of false anomalies. Select the sensitivity to reduce the number of false anomalies.
The anomalies are displayed:
on the Response Time graph for the entire test:
on the Response Time graph for the selected transaction, for example:
To analyze anomalies in Grafana, click on an anomaly point and click the Go to Grafana link.
Stop a test#
To stop a test, use one of the following methods:
in the Test runs in progress pane of the Test Runs page, click
.In the details test page, click Stop.
The test stops after a while.
View results#
After the test is completed, thе page has the following data:
JMeter LOG file:
The Throughput and Response Time graphics.
SLA execution status. You can also add SLA after the test is completed. For more information, see Configure SLA.
Note
If the completed test meets the conditions of the trend report, the trend report will be updated. For more information, see Trend reports.
For more information, see Load Test Analysis.
Run a debugging test#
Debugging allow you to check the test. PFLB Platform overrides the user’s test settings:
The test runs with 1 VUser in each group.
The test runs for 5 minutes or 10 iterations of the test, whichever comes first.
To run a debugging test, on the Load profile tab, click the Debug run toggle and click Run.
View detailed data about requests and responses#
The debug.jtl file contains detailed information about requests and responses. The link to the file becomes available after the debugging test is completed:
For more information, see Apache JMeter Wiki.