Katalon Studio is provided by the vendor as a free and robust automation solution for API, Web and Mobile testing. It is designed to eliminate the complexities of building an automation framework by integrating all necessary test components with built-in keywords and project templates. Katalon Studio includes a full feature set for a complete test automation process covering multiple platforms and testing types. New users can get started with test automation using its easy-to-use…
$69
per month
Tricentis qTest
Score 8.5 out of 10
N/A
Tricentis qTest (formerly QASymphony) provides enterprise-level agile testing tools giving businesses visibility and control needed to ensure application quality in fast-paced development environments. Tricentis and QASymphony merged in summer 2018.
$1,200
per year per user
Pricing
Katalon
Tricentis qTest
Editions & Modules
Node Locked License
$69.00
per month
Floating License
$1,529.00
per year
No answers on this topic
Offerings
Pricing Offerings
Katalon
Tricentis qTest
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
Katalon Studio was originated from KMS Technology R&D. It has been a successful solution for numerous automation projects ranging from small team to enterprise client.
Katalon Studio is free for use, product development is funded by the testing services provided by KMS Technology. To support future releases, please consider subscribing to our business support services.
Extensive integration options with various third-party tools, enabling seamless integration into existing workflows. Allows for flexibility and customization of workflows, fields, and permissions to adapt to unique testing requirements. Supports robust requirements traceability, …
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.
Tricentis qTest integrates seamlessly with Jira, making it ideal for teams that manage user stories and defects in Jira while keeping test cases and execution in qTest. When paired with automation tools like tosca, Selenium, or WebdriverIO, qTest is excellent for aggregating both manual and automated test results in one place.
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.
As a fresher, when I started using qTest it was very handy and easy to understand.
It helps us trace the test cases that are used to test the quality in a single location
The main thing is its integration with JIRA as soon as we create a ticket we would be getting all the requirements in the qTest so it became easy for me
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.
In requirements , we can't add multiple test cases at once, or search multiple cases at once, need to do one by one. Here actually qtest needs to improve.
Linking cloud hosted qtest and on-premise TOSCA is very difficult especially when you are working with client system with security wall. It requires tunnelling software which is not recommended.
It successfully balances deep enterprise functionality with a clean and modern interface. One of its strongest points is the intuitive, folder based navigation, which makes organizing test case and cycles feel natural. Learning curve is relatively shallow for the new team members to become productive without extensive onboarding. Also the deep integration with JIRA is a significant boost to its usability.
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.
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.
All of them offer formidable solutions in the test management realm, but each one caters to different niche and need. qTest distinguishes itself with its deep integration capabilities, especially with Agile and DevOps tools, enabling streamlined CI/CD process. Its modern, user-centric interface contrasts with ALM's more dated appearance and complex setup. While TestRail provides a clean user experience and caters to a broad spectrum of business, qTest's scalability, from SMBs to large enterprises, stands out. PractiTest's cloud-based solution is geared towards mid-sized companies, but qTest's flexibility, advanced analytics, and robust reporting grant teams actionable insights. qTest' approach to a more holistic test management closely aligning with modern software development practices
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.
