Gatling Enterprise vs. Katalon

Gatling requires Scala code to run high-quality scenarios. The recorder helps, but does not provide an immediately usable path. In the results, it is difficult to analyse the errors encountered during a load test. We can identify when errors occur, but it is challenging to pinpoint the cause at a given moment.

Incentivized

Katalon TestOps is well suited for an oraganization who want to organize their automation collections and have everything in one place. It provides good insight on test runs, failures and also helps in defect tracking. It is extremely easy to schedule and run test suites automatically. With the help of test history, it becomes easier to triage the report and identify if it is a product issue or a test flakiness. Also with the automation run scheduling features with custom options, user do not have to manually trigger the runs and just run the scheduler to do the job.

Incentivized

• Quick simple report.
• Heavy loads.
• API test.

Incentivized

• Easy to setup and quick to get started: As Katalon comes with built-in features a new automation tester can automate easily. Script creation time is quick.
• Test Analytics: Katalon also provides analytics which tells you the pattern of your automated tests at a different instance of time.
• Third Party Integration: Katalon provides amazing integration with 3rd party tools like JIRA, ALM, GIT, JENKINS, etc.
• Image-based testing: Katalon also provides inbuilt image based test automation.

Incentivized

• Scripting with user interface.
• More reports.
• Recording user path.

Incentivized

• Integration with Azure is painstakingly slow as it takes too much time to upload reports to Azure. When raised with the support team i was advised to contact Microsoft who promptly and correctly replied that its an issue with the katalon plugin.
• Non Responsive Customer Support. Several mails were replied late.
• The Desktop app uses too much memory when booting up and running tests even on a 16gb RAM.

Our tests are only run via an integration platform (Jenkins), and only the results are analysed using Gatling reports. The difficulty lies in maintaining the Scala scripts, which must keep pace with changes in the application over time. New use cases must be thoroughly documented for testers who are not directly involved in development.

Incentivized

Due to the slowness, there is an intermediate timeout. There is no other problem.

Incentivized

I love the support. They have provided answers and solutions for most of our questions or doubts that could come up. They also have provided basic tutorials on how to get familiarized with the program.

Incentivized

Gatling can only be used for high-load tests with a paid license and only for tests with a reduced graphical user interface (GUI). Unlike OctoPerf, NeoLoad, or LoadRunner, we are not limited to a fixed number of users per license. Compared with JMeter, Gatling is less resource-intensive and therefore does not require an extensive test infrastructure.

Incentivized

Katalon Studio is above both the tools is due to its codeless test automation feature and having API, desktop, web, and mobile automation in one place but obviously there is room for improvement when desktop automation is of primary importance in the automation.

Incentivized

• Re use existing use case.
• Difficult to add other load generator.
• Cost reduction for simple tests.

Incentivized

• Support can be better: As mentioned before, katlon community is still growing but is currently a small community. If you are stuck, its hard to find help in the community and one has to reach out to the support for help. This takes a while before you can get solution to your problem.
• Result upload takes little longer time: It is been observed that uploading tests results takes little longer.
• Sometimes it gets hard to integrate: Since this is fairly a new tool, requires lot of learning curve to get the job done effectively.

Incentivized