Katalon vs. Selenium

Free trial version is fine but you don't get the adequate support and VFM for the licensed version. Customer service needs to be improved a lot and any QA's with less technical background or less time to troubleshoot issues in the software on their own would find it difficult to use.

When you have to test the UI and how it behaves when certain actions are performed, you need something that can automate the browsers. This is where Selenium comes to the rescue. If you have to test APIs and not the frontend (UI), I would recommend going with other libraries that support HTTP Requests. Selenium is good only when you have no choice but to run the steps on a browser.

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

• For any web based UI automation, Selenium is the best tool out there to automate your tests.
• It supports multiple coding languages like Java, Python, Ruby, C# etc.. to choose from.
• There is a huge community of users and can get many answers on StackOverFlow.
• It has lot of other plugins to make your tests even more efficient.

Incentivized

• Katalon Studio supports only grovvy language for now. It will be nice to see support for other scripting languages.
• Performance issues; sudden crash of the tool.
• Debug button is provided only to licensed owner since Katalon 7+ version.
• New tool, few resources available to learn. So there is a mild learning curve here.

Incentivized

• Recognize Adobe Flash and MS Silver Light elements without additional help
• Detect and locate Java applets ingredients
• Having the "Wait-till-Displayed" or "Wait-till-Present" as a built in Web Driver function instead of requirement for writing loops and defining expliccit wait, visiblewait, invisiblewait, etc.

Incentivized

We love this product mainly because of its high customization abilities and the ease of use. Moreover, its free and can be learned easily through online communities and videos. The tests are more consistent and reliable as compared to Manual tests. It has enabled us to test a large number of features all in one go, which would have impossible through manual tests. The reports generated at the end of the tests are really helpful for the QA and the development teams to get a fair view of the application.

Incentivized

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

Incentivized

As I mentioned earlier, the reason I use Selenium is because there is a fairly widespread community of users, and user support services are at a good level. because the application is open source, it works on many platforms (Windows, Linux, IOS) without any problems. In addition, it gives us a lot of options for writing functional tests. For errors that we receive through the application, we can easily find the reasons for errors in the forums.

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

Selenium does not have technical support available easily. You have to go through forums to get the information you need. However, there are excellent forums out there that make it easy to troubleshoot. The open-source flexibility makes it difficult to have dedicated support.

Incentivized

We did everything we needed to use it. Now we can execute our tests on different operational systems and browsers running few tests simultaneously. We also implemented Appium framework to execute our tests on mobile devices, such as iPhones, iPads, Android phones and tablets. We use SauceLabs for our test execution and Jenkins for continuous integration.

Incentivized

Initially, our oragnization had to integrate Katalon tests with the Jenkins to schedule the test runs. The reports were stored in company local database. To identify test flakiness or product issue one had to dig deep into the reports. This issue was all solved by Katalon TestOps. Katalon TestOps provides report history in one place and also helps in easy triage of the report by pointing out script flakiness

Incentivized

At the time of adoption, there were not many other alternatives that were even close to being competitive when it comes to browser testing. As far as I know now to this day, there is still little competition to Selenium for what it does. Any other browser-based testing still utilises Selenium to interact with the browser.

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

• Generation of detailed finding reports helped in cost savings in regard to direct labor.
• Quality Assurance technicians found value in repeating mundane duties that they perform daily. It saved mental energy due to the automation process.
• The value was established in high volume usage in setting up meetings as well as new accounts with A/B testing. Also merely cleaning up old test documents by evaluating them and organization or deletion.

Incentivized