QMetry is a test management tool that offers test case authoring, reusable test cases, test execution, 140+ reports including deep traceability and test case coverage reports with customization options, and integrations with Jira, CI/CD tools like Bamboo/Jenkins, and Automation frameworks.
N/A
TestComplete
Score 8.0 out of 10
N/A
TestComplete is a GUI test automation tool that enables users of all skill levels to test the UI of every desktop, web, and mobile application. TestComplete is best suited for testers, automation engineers, and QA teams in any industry.
$2,256
per license
Pricing
QMetry
TestComplete
Editions & Modules
No answers on this topic
Node-Locked Base
2,256
per license
Node-Locked Pro
3,950
per license
Float - Base
5,077
per license
Float - Pro
7,901
per license
Offerings
Pricing Offerings
QMetry
TestComplete
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Pay for only the modules needed. TestComplete Pro includes all three modules: desktop, web, and mobile, at a bundled price point, as well as access to the parallel testing engine, TestExecute.
TestComplete has additional add-ons, including TestExecute and the Intelligent Quality Add-On.
More Pricing Information
Community Pulse
QMetry
TestComplete
Features
QMetry
TestComplete
Test Management
Comparison of Test Management features of Product A and Product B
QMetry, like any new-gen test management tool, works well with any type of development methodologies, be it agile, waterfall or hybrid. It is positioned to be a tool for enterprises of any size. QMetry also provides easy migration of existing test artifacts from a legacy test management tool to QMetry without loss of any information. The one thing that I see as an opportunity for improvement is trying to provide out-of-box integration with all major test automation tools. Another area could be to expand the offering to include it as a product suite with accessibility testing, security testing, performance testing, and test automation which is what the trend is.
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
TestComplete is great for working with our non-web applications.
TestComplete allows us to interface with our web application in a robust way.
Despite the age of our architecture, TestComplete handles the old stuff that's been around a while as well as the newer technology when we are able to implement it.
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.
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.
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
QMetry provides an easy path for migration from the legacy test management tool. The migration utility is free compared to other vendors. We have received great customer support from day one of the engagement starting with POC, implementation, and ongoing support. Overall, pricing and licensing model are affordable and attractive.
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.
Improved product quality overall, since automating tedious tests frees up time and is not prone to fatigue
When getting started - depending on the complexity of the software/UI tested - it can be a time sink before it brings actual value, and changes to the structure of the UI need to be communicated early, so the changes can be implemented on time to run the automation
Once set up, the maintenance cost is low, and the automation frees up a lot of resources especially in an agile environment where there are a lot of releases that would need regression tests.