Performance Test Report
Errors
This section lists all errors that occurred during the load test. The data listed here helps you identify application errors or test problems. More...Hide...
Errors are hard failures in the flow of testing. They stop the current execution of the test case (or transaction), log an error, and eventually move on to the next test execution if scheduled to do so.
Errors can occur on transaction, action, or request level. Errors on the request level are counted on action level as well. Action level errors are also counted as transaction errors. A connection reset, for instance, counts as request error and causes the action to fail (counted). As a result, the transaction fails as well which again is counted and logged.
The Overview section below lists the error message and the count. It ignores the stack trace to sum up common problems without relating them to the test case. The Details section beneath lists the full stack trace next to the test case and the directory in which you can find the data dump for further analysis.

Request Errors
This section displays the request errors grouped by response code. More...Hide...
The chart creation can be configured by setting the corresponding report generator properties. (See reportgenerator.properties file for more details)

Transaction Error Overview
Error Message | Count | Percentage |
---|---|---|
Totals (1 entry) | 8 | 100.0% |
java.lang.AssertionError: expected:<200> but was:<503> | 8 | 100.0% |
More...Hide...
The chart limit can be set or disabled by setting the corresponding report generator properties. (See reportgenerator.properties file for more details)
Transaction Error Details
More...Hide...
The chart limit can be set or disabled by setting the corresponding report generator properties. (See reportgenerator.properties file for more details)
Count | Test Case | Action | Directory | Error Information |
---|---|---|---|---|
8 | EchoLatency | EchoLatency | ac0004_us-central1_00/EchoLatency/187/output/1733753051122 ac0007_us-central1_00/EchoLatency/244/output/1733753051634 ac0008_us-central1_00/EchoLatency/34/output/1733753726878 ac0011_us-central1_00/EchoLatency/72/output/1733754213423 ac0014_us-central1_00/EchoLatency/17/output/1733753679820 ac0016_us-central1_00/EchoLatency/457/output/1733753050770 ac0019_us-central1_00/EchoLatency/126/output/1733753621814 ac0020_us-central1_00/EchoLatency/491/output/1733753682886 |
java.lang.AssertionError: expected:<200> but was:<503>
java.lang.RuntimeException: java.lang.AssertionError: expected:<200> but was:<503> at com.xceptance.loadtest.api.util.Actions$1.execute(Actions.java:41) at com.xceptance.xlt.api.actions.AbstractAction.run(AbstractAction.java:359) at com.xceptance.loadtest.api.util.Actions$1.run(Actions.java:58) at com.xceptance.loadtest.api.util.Actions.run(Actions.java:67) at com.xceptance.performulator.loadtest.tests.echo.EchoLatency.test(EchoLatency.java:16) at com.xceptance.loadtest.api.tests.RESTTestCase.run(RESTTestCase.java:117) ... Caused by: java.lang.AssertionError: expected:<200> but was:<503> at org.junit.Assert.fail(Assert.java:89) at org.junit.Assert.failNotEquals(Assert.java:835) at org.junit.Assert.assertEquals(Assert.java:647) at org.junit.Assert.assertEquals(Assert.java:633) at com.xceptance.performulator.loadtest.tests.echo.EchoLatency.lambda$test$0(EchoLatency.java:25) at com.xceptance.loadtest.api.util.Actions$1.execute(Actions.java:36) ... 43 more ![]() |