Selenium vs. TestComplete vs. Tricentis qTest

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

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

• 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

• 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

• Selenium is pretty user-friendly but sometimes tests tend to flake out. I'd say roughly one out of twenty tests yields a false positive.
• Selenium software cannot read images. This is a minor negative because a free plug-in is available from alternate sources.
• Slowness may be a minor factor with Selenium, though this is an issue with basically any testing software since waiting on a site to execute JavaScript requires the browser to wait for a particular action.

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

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

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

For those who are unfamiliar with coding, there is a bit of a learning curve. There is plenty of helpful documentation and resources but it can take a little time to get the software up and running. Once you get the hang of how Selenium works, and what it can do, you realize how many things you can use it for, and how many processes you can automate.

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

The Selenium app has a pretty fat community of users. For the problems we are experiencing, we are primarily receiving support from these communities. In addition, there is widespread service support. Instant support is given to the problems we experience when we need Online support. We and our team are happy to provide this support, especially before important deployment processes

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

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

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

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

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

• There hasn’t been a downside to using it yet other than we’ve got to update the programs we create for each change.
• This has saved us hundreds of hours of manpower by allowing our automation engineer to rapid fire tests.
• We are able to screenshot and save entire sites before and after launch with a program the automation engineer created
• We can compare large volumes of data against data in excel docs with a program created using Selenium

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