Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

JMeter how to NOT fail 500 Internal Server Errors

I am using JMeter as a unit test tool, in parameterised calls where I expect some of the responses to be 500 internal server errors. I am using BeanShell Assertions to check the responses.

I want some of the 500 internal server errors to NOT be marked as failures if the response contains a specified text. All 500 server errors are marked as failures. Is it possible to change the behavior?

Below is an extract from the BeanShell Assertion.

if (ResponseCode.equals("500")) {     Failure = false;     String respData = new String(ResponseData);      if (! respData.contains("specific Text")) {         Failure = true;         FailureMessage = "500 Internal Server Error:  Unexpected Response.   " +              "Response Message: " + respData;     } }   

Thank you and Regards

like image 518
Gazen Ganados Avatar asked Mar 20 '12 11:03

Gazen Ganados


People also ask

What are the main reasons for receiving 500 internal server error?

The 500 Internal Server error could be caused by an error during the execution of any policy within Edge or by an error on the target/backend server. The HTTP status code 500 is a generic error response. It means that the server encountered an unexpected condition that prevented it from fulfilling the request.


1 Answers

Another possible solution is to use Response Assertion with checked "Ignore Status" flag added to your sampler:

Ignore status
Instructs JMeter to set the status to success initially.

The overall success of the sample is determined by combining the result of the assertion with the existing Response status. When the Ignore Status checkbox is selected, the Response status is forced to successful before evaluating the Assertion.

HTTP Responses with statuses in the 4xx and 5xx ranges are normally regarded as unsuccessful. The "Ignore status" checkbox can be used to set the status successful before performing further checks. Note that this will have the effect of clearing any previous assertion failures, so make sure that this is only set on the first assertion.

like image 160
Aliaksandr Belik Avatar answered Sep 24 '22 13:09

Aliaksandr Belik