Katalon Test Ops vs TestRail comparison

"I noticed that only the enterprise version has integration with GitHub."

"Katalon Test Ops has AI features that speed up the process by automating tasks that would otherwise be done manually."

"It's more user-friendly as a solution."

"From a testing perspective, the management is awesome. I am able to do testing and then add the reporting and the evidence. It is fair in terms of the price that you're paying. You get what you're paying for."

"The most valuable features are the flexibility, ease of use for writing new test cases, the test plans, and the composition."

"The most valuable features are the reporting in the dashboard and the general way in which we can create test runs is helpful."

"The product helps us create test cases and reports."

"The ability to time test runs gives the tester the ability to compare calculated times to actual times it takes for a test case to run."

"I use the solution for test management."

"The integration with Jira and the ability for extra configurations are the most valuable features."

"Integration with Confluence and JIRA."

"The execution module of Katalon Test Ops may need some improvement, especially when running a high volume of test scripts."

"The free version is limited."

"There are stability troubles. My area does not have a good connection. That's why sometimes I face issues."

"The reports should be more user-friendly."

"I do see room for lots of improvement in it. In terms of usability, duplication with test cases and constant creation of projects isn't easy. There is also too much API integration into automation tools, which is not there in ALM with UFT. Instead of setting it up as a project and using it, we set it up as a system for usability. It also lacks in the traceability aspect. For traceability, you need to use the JIRA plugin and drag traceability on JIRA, but the functionality is still quite limited. The biggest gap is mainframe testing. It would be good if I could start with mainframe testing. Manual granting of access is another issue. There is no API that I could use with another system where it is automated. There is an API for loading somebody to a project but not for adding to the application."

"It would be nice to have a description section when creating the test scenario itself so I can indicate what the configuration should be."

"The platform needs improvement regarding performance and creating links."

"I have faced some issues with the integration between TestRail and Jira, which haven't been permanently resolved yet."

"The TestRail API to integrate reporting of automated tests is complete, but requires many requests to identify the appropriate entry."

"The test suite management has room for improvement as well as better reporting."

"With TestRail, the APIs are there, but they may not be able to easily integrate with the Jenkins."

"I give the price a five out of ten."

"Its price is definitely not more. If they introduce automation, they can charge more."

"The price of the solution is based on how many users you have per year. When you grow, it is segmented, For example, 10 to 25, you have a price, and more than 50, or 100, you need to take the enterprise license. I don't think we will reach this point."

"My advice to others is to shop around for the best deal. Some options out there are free in cyberspace."

"The product is not much expensive."

"Negotiate the best deal you can."

"Use TestRail Cloud (online TR hosted server) and don't worry about maintenance or scalability. It saves a lot of cash and time."

"The product has a reasonable price in terms of the features."