Likelihood to Recommend 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
Read full review The qTest is well-suited for organizations transitioning to Agile or DevOps frameworks. It Streamlines test management with real-time collaboration and integrates with popular CI/CD tools. It excels in complex, large-scale projects needing centralized test cases management, traceability, and detailed reporting. However, organizations on a tight budget might find it cost prohibitive compared to simpler, low-cost alternatives.
Read full review Pros 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. Read full review Highly customizable: we were able to organize our test cases in unique ways that made our work easier. Connectivity with Jira: being able to pull requirements information in from Jira was a big point for us. Standalone tool: Being a standalone tool on a dedicated server, we were able to have access to our tests regardless of whether our Jira server was down. Read full review Cons 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. Read full review 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. Read full review Likelihood to Renew This has been a core QA management tool for our organization and integrates well with our other SDLC platforms (Azure DevOps/Jira/Katalon).
Read full review Usability qTest is actually intuitive and user-friendly, despite my other scathing review aspects
Nick Larsen Quality Assurance Manager - Application Development & Support
Read full review Support Rating The actual answer is 0. I have never experienced worse support, whether personal or professional
Nick Larsen Quality Assurance Manager - Application Development & Support
Read full review Implementation Rating Again, supporting documentation could have been a lot better
Nick Larsen Quality Assurance Manager - Application Development & Support
Read full review Alternatives Considered 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.
Read full review 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, ensuring comprehensive test coverage. Lastly management decisions too
Read full review Return on Investment 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. Read full review Better organization and centralization of test cases has led to more cohesive team collaboration Speed to delivery, deployments to production, are mostly maintained Performance issues have led to testing delays requiring the team to switch to other methods which contributed to QA bottleneck issues and sometimes even missed sprint commitments Read full review ScreenShots Tricentis qTest Screenshots