Appium vs. TestComplete vs. Tricentis qTest

1. It's open source which supports range of languages, operating systems and languages. Well suited for Android and IOS mobile automation. Supports all kinds of apps, which makes it flexible and robust mobile testing tool 2. It is less appropriate where we need intercept network call to verify the API calls. Extensive coding experience is required to work Appium

Incentivized

Best suited to smaller unit test or tests broken up, couple of forms at a time Not suited - larger regressions test involving multiple systems. - my main regression involving payments has been unsuccessful for the last 3 years despite all working fine separately and while being watched

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.

Incentivized

• It uses WebDriver API so it makes it easy to use for former web test automation engineers.
• It can be managed via the command line via an extensive set of parameters.
• It handles implicit waits at the server side that is especially valuable in distributed infrastructure.

Incentivized

• Identifying UI objects and application structure
• Expandability of tests through scripts and script extensions/plugins
• low barrier of entry (you can get started quickly, and other's don't need much explanation to contribute on a basic level)
• Possibility of Jira integration for reporting
• Relatively few (and usually easy to solve) git conflicts when working simultaneously
• easy handling of test data, also for iterative tests

Incentivized

• 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

• Element browser sometimes is unreliable and has sporadic fails.
• Appium running is a bit slow, compared to tests written with Appium and with Espresso or XCTest.

Incentivized

• TestComplete could stand to have a simplified view for different types of users. For instance, as a manager/architecture guy, I'm not so interested in getting into the code and am more interested in file-based interactions.
• TestComplete could use more integration with reporting for things like TeamCity to improve test status visibility.

Incentivized

• 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.

Incentivized

I am rating 10/10 because Appium can use with multiple programming languages with multiple Test engines. Also, it works for both Android and iOS.

Incentivized

We have bigger test automation pack using test complete at the same time we also think this is not good performing tool for large number of test automation scripts.

Incentivized

This has been a core QA management tool for our organization and integrates well with our other SDLC platforms (Azure DevOps/Jira/Katalon).

Incentivized

I would like to give 9/10 rating to Appium because of it can easily integrate with popular frameworks and CI/CD tools, as well as it is reliable, flexible and easy to use. The setup can bit complex in initial step, but once on configured it's very easy to use and enables stable and scalable mobile automation for real and cloud devices.

Incentivized

It is usable when you become accustomed to its quirks. Not using it for two months and then you need to re-learn the quirks for some features (but some quirks are so awful that they will never fade from your memory). So, when using it regularly, it is possible to be quite productive, if no big correction in name mapping is needed.

Incentivized

qTest is actually intuitive and user-friendly, despite my other scathing review aspects

Incentivized

Some bugs were quickly resolved, but most UX quirks of the tool are just marked "as designed". No follow up for enhancement request.

Incentivized

The actual answer is 0. I have never experienced worse support, whether personal or professional

Incentivized

If you develop a mobile application and your testing process goes in cloud, probably you will face a problem - how to implement a stable connection between your mobile devices and testing servers

Incentivized

Again, supporting documentation could have been a lot better

Incentivized

If you're an Apple developer, you use Xcode. It's practically a forced necessity. For system testing though, it doesn't have to be. You can have your development team focus on unit and integration tests in their platform and another team automate acceptance tests with a language they are more familiar with.

Incentivized

TestComplete stacks up against them in terms of GUI and seamless performance. It records each and every step and action been performed in the application and produces a detailed report in a well-structured manner. It can connect and access seamlessly among various databases directly to speed up the testing process.

Incentivized

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

Incentivized

• Appium is open source, so it's free. That's budget friendly right there.
• The ability to write mobile automation tests has saved considerable time for our manual test team, but that is true with most automation tests.
• We use Sauce Labs with our other automation, but Appium works great with Sauce Labs, as well, if I needed to run on emulators and simulators.

Incentivized

• Saves hundreds of man-hours with either QA testing or data entry
• With the small cost of the product, it has saved the company money with both employee costs as well as the cost of mistakes made by human error or software bugs

Incentivized

• In comparison to other Testing tools, Tricentis qTest was the most expensive.
• We were able to quickly bring international users up to speed on how to use the tool.
• The ability to clone a project rather than create a new one from scratch was a valuable time saver.

Incentivized