Handling Errors


I’ve been testing on an application using Gatling. I was able to simulate several scenarios but they contain lots of errors. I’ve already “cleaned” them by removing some lines that I think not necessary. Most of these errors are the following:

status.find.in(200,304,201,202,203,204,205,206,207,208,209), but actually found 403


java.io.IOException: Remotely closed

How do I handle these kinds of errors? How do I validate and make the test successful?

Please help. Thanks!

This a server error. For performance test, you would want to report these errors. It tells the developers that application can’t handle load.

Hi Abhinav,

Which particular error are you referring to? What does the other error tells? And what action should I do about it?

I didn’t see the http status code last time. https://en.wikipedia.org/wiki/HTTP_403 - Unauthorized access.

You are not authenticated. You need to figure which authentication method is used by application and apply it with Gatling.

I will have to research on that. I will inform you as soon as I find answers. Thanks Abhinav! :slight_smile: