OpenText Functional Testing and Qt Squish are functional testing tools competing in the domain of software test automation. OpenText Functional Testing seems to have an edge due to its comprehensive features and AI support, which are appealing for enterprise solutions, while Qt Squish is advantageous in environments using Qt frameworks, with robust object identification.
Features: OpenText Functional Testing offers advanced automation capabilities, compatibility with various technologies, and leverages AI for test creation. It is suitable for complex enterprise-level applications. Qt Squish shines in environments using Qt frameworks, offering strong support for object identification and remote testing capabilities, and has multiple scripting language support.
Room for Improvement: OpenText Functional Testing needs enhancements in stability, support for modern languages, refinement of AI features, and simplification of its licensing model. Qt Squish, although integrated well with Qt, is costly, and can improve in IDE support and expand integration capabilities.
Ease of Deployment and Customer Service: OpenText Functional Testing offers flexibility with deployment in cloud environments but experiences variable customer support. Qt Squish, typically on-premises, is praised for its straightforward setup, but like OpenText, its technical support could improve in responsiveness and depth.
Pricing and ROI: OpenText Functional Testing is known for its high costs and licensing complexity but offers substantial ROI over time for large enterprises with its expansive feature set. Qt Squish is also seen as an expensive solution, though its simpler licensing model can justify its investment, especially in Qt-centric environments.
The development time using UFT can be cut down into half as compared to coding from scratch.
Automation is done very fast, leading to improvements in the QA process and reducing the time needed for test automation.
We can easily achieve a return on investment in one, two, or three years.
For the part that has been automated in Qt, not everything is suitable for automation.
Organizations can't wait for this lengthy process, especially when they are under pressure with their timelines.
Support cases are easily created and attended to promptly, depending on urgency.
The technical support is rated eight out of ten.
Running them in parallel allows you to consume multiple runtime licenses and just execute the tests that don't have conflicting priorities and get through a lot of volume much quicker.
The tool can be installed on all computers used by developers or test automation engineers.
With one license, just one user or one test scenario can be run at a time.
One of the key stability issues was that Windows would consume memory without releasing it, leading to regression testing crashes.
Incorporating behavior-driven development tests would enhance the capabilities of UFT One.
We frequently encountered stability issues when the browser dependency caused Windows to consume memory without releasing it, leading to crashes during regression testing.
If it could move closer to a no-code or low-code solution, it might dominate the market again.
If you want to run it for different versions of the software, then you need the Qt version of Java.
There are many open-source tools with no cost, and there are no-code tools that are less expensive than UFT.
The pricing or licensing policy of OpenText is a bit expensive, however, it's one of the best solutions in the market.
It's cheaper than Tricentis Tosca but more expensive than some others.
For the developer license, it is about $5200 a year.
UFT supports Oracle, SAP, PeopleSoft, and other non-web applications, making automation feasible.
OpenText Functional Testing has an impressive ability to connect to mobile devices and its ability to test so many different types of software, whether it be mainframe, APIs, mobile, web, or desktop.
The best features of OpenText Functional Testing include descriptive programming, the ability to add objects in the repository, and its ease of use for UI compared to other tools.
For the parts that have been automated in Qt, not everything is suitable for automation.
| Product | Mindshare (%) |
|---|---|
| OpenText Functional Testing | 7.0% |
| Qt Squish | 2.4% |
| Other | 90.6% |
| Company Size | Count |
|---|---|
| Small Business | 20 |
| Midsize Enterprise | 13 |
| Large Enterprise | 74 |
| Company Size | Count |
|---|---|
| Small Business | 10 |
| Midsize Enterprise | 2 |
| Large Enterprise | 9 |
OpenText Functional Testing provides automated testing with compatibility across technologies, browsers, and platforms. It targets APIs, GUIs, and applications like SAP and Oracle for efficient test automation, emphasizing usability and integration with tools such as Jenkins and ALM.
OpenText Functional Testing offers wide-ranging automation capabilities for functional and regression testing, API testing, and automation across web, desktop, and mainframe applications. It supports script recording and object identification, appealing to less technical users. Despite its advantages, it grapples with memory issues, stability concerns, and a challenging scripting environment. Its VBScript reliance limits flexibility, generating demand for enhanced language support and speed improvement. Users appreciate its role in continuous integration and deployment processes, managing test data efficiently, and reducing manual testing efforts.
What are the key features of OpenText Functional Testing?In industries like finance and healthcare, OpenText Functional Testing is leveraged for end-to-end automation, ensuring streamlined processes and accuracy in testing. Many companies utilize it for efficient test data management and integrating testing within continuous integration/deployment operations.
Qt Squish is a versatile testing tool that supports Python, integrates with Rational Quality Manager, and handles multiple toolkits. It efficiently boosts code quality with features like auto-completion and a comprehensive dashboard while supporting diverse languages and providing strong documentation.
Qt Squish is known for its robust capability in automatic testing, particularly in GUI and regression testing applications across real-time control, embedded systems, and hybrid frameworks. The tool enables behavior-driven development with Gherkin Syntax, integrates seamlessly with CI/CD pipelines, and facilitates effective data-driven and distributed batch testing. Users gain significant value from its compatibility with Qt applications, multiple platforms, extensive language support, and integration with other development tools. Although there are suggestions for improving reporting, configuration for less technical users, Git integration, and object identification, Qt Squish still stands out for its exceptional capability in mapping UI components and supporting automated UI testing.
What are the important features of Qt Squish?Industries such as real-time traffic control, embedded systems, and hybrid applications frequently use Qt Squish for automated testing. The ability to integrate with CI/CD pipelines and compatibility with multiple scripting languages makes it an ideal solution for organizations focusing on GUI and regression testing. Companies benefit from its seamless integration with diverse data sources and development tools, enabling efficient automated UI testing across all relevant platforms.
We monitor all Test Automation Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
