Test Execution Fail Reasons
Last updated
Was this helpful?
Last updated
Was this helpful?
Loadium test executions can occasionally be interrupted due to user-side misconfigurations, missing data, or network access issues. This guide addresses the most common problems and their solutions.
Typo in csv dataset config.
Giving an invalid file extension in csv dataset config.
An incorrect CSV format can cause JMeter tests to fail unexpectedly. Issues such as the wrong number of columns, incorrect headers, or mismatched data types often lead to errors during test execution. To ensure proper functionality, the CSV file must be correctly formatted and aligned with the test plan's requirements, providing the necessary data accurately.
Loadium initializes virtual machines for load tests from cloud providers such as AWS, Azure, and GCP. If the target environment is restricted from public access, the virtual machines may not be able to connect, preventing the test from starting.
The versions of the plugins used in the test scripts are not up to date, the tests may start properly.
An invalid JMX file in JMeter tests can cause tests to fail before they start.
Common issues include:
Syntax errors
Corrupted elements
Unsupported font types (such as non-Latin characters)
Missing configurations within the JMX file.
These errors prevent Loadium from properly executing the test file, leading to failures. It's essential to validate and correct the JMX file to ensure smooth and successful test execution.
In cases where the first HTTP response (from any request) during a performance test takes more than 120 seconds to return to Loadium, it may be labeled as 'failed' by the system. Ensure that your virtual user load configuration (e.g., ramp-up time) is appropriate for the target environment, or consider using a monitoring tool to check your services.
Similarly, at any point during the test, if no data is received for 120 seconds, the system may label it as 'failed'.
