Aside from the available documentation (Tutorial), is there any available reading material or documentation that tackles Effective Performance Testing and Reporting using Gatling? Or do you happen to run into one? I have searched on the web but they are approaches on other Perf Testing tools. I want to learn more about Gatling and how to effectively use it as a Performance Testing tool, especially how to interpret the results gathered after execution. Any tips?
I am pretty sure I am not the only one who needs this. I am not much of a technical person so a very comprehensive and straightforward how-to manual would do a lot of help.
Have you checked gatling online resources? http://gatling.io/docs/2.1.7/project/online_resources.html A good share of articles, maybe some vids else google ebay gatling load testing. Is there anything in particular you need from the gatling graph or need help interpreting it? Let me know if I can help in anyway. I am not gatling expert, but I have been using it for good time now and enjoy it.
I’m sincerely glad that you replied to my query. I believe the link that you have given me would be a great help. I am currently working on testing on several applications but I am always worried if I am interpreting and delivering the results correctly. I’m having a hard time dealing with errors. I am not sure what a particular error tells and what must I do to correct them. (For example: status.find.in(200,304,201,202,203,204,205,206,207,208,209), but actually found 403 - or - java.io.IOException: Remotely closed).
I am dying to learn more about Gatling as I am the only one who uses it in our company and I have no one to ask help from, so I post my queries in this forum, do some research and a little bit of practice of the tool. Plus, I really think Gatling is a promising tool and I actually enjoy using it even though I am just a beginner.
Can you please share how you usually do your tests using Gatling? And if you could also share the best practices that you have learned from your experiences in using the tool.
Howdy Julian,
Glad to hear the material was useful. I can definitely share my thoughts on gatling and practices I have used to get it working for the company I am at. The 403 that is spit out from the logs usually means something with unauth access. I am not sure what your script does, but you may need to have a save a token and resuse it through your script. See here: http://gatling.io/docs/2.1.7/http/http_check.html#http-check-saving
Some tips:
-Separate the request vs the simualtions ( I try to apply Page object pattern)
-Use some build tool- Gradle, Sbt, Maven(what ever flavor you like ) http://gatling.io/docs/2.1.7/extensions/index.html
Glad to hear the material was useful. I can definitely share my thoughts on gatling and practices I have used to get it working for the company I am at.
Absolutely. Thanks again. I definitely need some guides on this. Teach me, master.
The 403 that is spit out from the logs usually means something with unauth access. I am not sure what your script does, but you may need to have a save a token and resuse it through your script. See here: http://gatling.io/docs/2.1.7/http/http_check.html#http-check-saving
If I am not mistaken, this has something to do with SSL certificates? What I simply did was use https instead of http in the url while recording the simulation.
On the whole, how do you handle errors found after executing the scripts? Do you include them in your report or fix the script first to eliminate them?
Some tips:
-Separate the request vs the simualtions ( I try to apply Page object pattern)
I’ve thought of this already but haven’t applied it yet. I will have a try on the Page Object as you’ve suggested. Currently, I organize my scripts by isolating each process and storing them into objects (singleton). If you could provide a sample script using the Page Object pattern, please do. Thanks.