Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

200 ok response code is considered as error in blazemeter

 
poorna alluri
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am new to load testing . We created scripts in jmeter and are running actual load tests on blaze meter.
the issue we are facing right now is the response code 200 is also getting considered as errors which is increasing our total error % in the aggregate report.

Response codes
response code count response message
Non HTTP response code: java.net.SocketException 2479 Non HTTP response message: Connection reset
200 44066 OK

In our understanding 200 response code is success but they are counted as error in blaze meter. this does not happen in jmeter . so all 44066 requests are considered as errors.
due to this our error% in aggregate report shows really high values.
Another issue is requests which are shown as failed in assertions are not considered as errors.

Assertions
assertion name count assertion message
Assert the Sueccess/Failure 688 Test failed: text expected not to contain /Sorry/
Response Assertion 362 Test failed: code expected to contain /200/

The above are not considered as errors in blazemeter

Any information on this would be helpful. is it some thing we could change in the script.Please help us understand more on this.


 
Vitali Diho
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In JMeter , Response code of 200 can be counted as an error in several cases:
Assertion - for example you assertion set to look for some text in your reply and it wasn't there.
Embedded resources - for example you load HTML page with CSS, Images and JavaScript, and one or more of those resources where not found, then the whole Sample will be counted as failed.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic