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.
| Product | Mindshare (%) |
|---|---|
| Qt Squish | 2.4% |
| Tricentis Tosca | 11.0% |
| OpenText Functional Testing | 7.0% |
| Other | 79.6% |
| Type | Title | Date | |
|---|---|---|---|
| Category | Test Automation Tools | Jun 23, 2026 | Download |
| Product | Reviews, tips, and advice from real users | Jun 23, 2026 | Download |
| Comparison | Qt Squish vs Tricentis Tosca | Jun 23, 2026 | Download |
| Comparison | Qt Squish vs Katalon Studio | Jun 23, 2026 | Download |
| Comparison | Qt Squish vs Worksoft Certify | Jun 23, 2026 | Download |
| Title | Rating | Mindshare | Recommending | |
|---|---|---|---|---|
| Tricentis Tosca | 4.1 | 11.0% | 96% | 113 interviewsAdd to research |
| OpenText Functional Testing | 4.0 | 7.0% | 87% | 98 interviewsAdd to research |
| Company Size | Count |
|---|---|
| Small Business | 8 |
| Midsize Enterprise | 2 |
| Large Enterprise | 7 |
| Company Size | Count |
|---|---|
| Small Business | 197 |
| Midsize Enterprise | 81 |
| Large Enterprise | 285 |
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.
Qt Squish was previously known as froglogic Squish.
Google, Nokia, Pfizer, Siemens, Synopsys, Airbus, Boeing, Mercedes Benz, Disney, Shell, Reuters, Vodafone, XILINX, GE, Ericsson
| Author info | Rating | Review Summary |
|---|---|---|
| Software Test Engineer at Infrabel | 4.0 | I use Qt Squish mainly for regression and automatic regression tests, focusing on GUI-related testing in Qt. While it supports java SWT, setting up different software versions is cumbersome and requires specific environment variables. Other teams are considering additional tools. |
| Software Engineer at Ambu GmbH | 4.5 | We use Qt Squish for test automation in our embedded systems, offering valuable integration with Qt for UI tests. While effective, improvements are needed in the embedded environment and ease of upgrading, as integrating upgrades can be bothersome. |
| Software Test Engineer at Infrabel | 4.0 | I use Squish to control traffic in real-time. The virtual dashboard is a valuable feature, allowing me to view customer results at any time, although I believe the price could be improved. I switched from HP based on colleagues' recommendations. |
| Test Automation Specialist at a pharma/biotech company with 1,001-5,000 employees | 4.0 | I use froglogic Squish for automatic software testing, particularly user interface testing. Its modular framework and platform independence are valuable, but it could improve basic functionalities like login procedures and multi-screen handling. Overall, it enhances testing adaptability across platforms. |
| QA at a tech company with 11-50 employees | 4.0 | I use Froglogic Squish for desktop UI testing and appreciate its user-friendly interface and capability to test Qt applications. While I miss Git integration for collaboration, I expect the tool to be valuable and yield a return on investment. |
| Head - Solution Management Group at Meteonic Innovation Pvt. Ltd. | 5.0 | I use froglogic Squish for GUI regression testing with Qt frameworks. It's seamless across Windows and Linux. Although it's strong in GUI testing, adding performance and penetration testing could enhance its value. A centralized dashboard is available for monitoring. |
| Quality Assurance Engineer at a computer software company with 201-500 employees | 4.0 | I use Froglogic for automation QA and value its cross-platform QT support and integrated tools. My main issues are the IDE's lack of suggestions, slow saving, and the poor Jenkins CI integration. |
| Software Solutions Engineer at Meteonic Innovation Pvt. Ltd. | 5.0 | Squish excels in table-driven and BDD testing, integrating easily with various tools. It's powerful for hybrid apps, remote testing, and now offers OCR. Although very good, I wish it supported C/C++ applications without Qt. |
| Sr. Software Solution Engineer at Meteonic Innovation Pvt Ltd at Meteonic Innovation Pvt. Ltd. | 5.0 | I found Squish to be the best GUI testing tool. Its object-based approach delivers consistent, reusable, OS-independent test scripts for my hybrid applications, integrating perfectly with CI and significantly improving our automation. |
| Product Specialist at a tech services company with 11-50 employees | 5.0 | I found Squish automates GUI tests well, supporting various languages and BDD. Installation was simple, and customer service good. My main challenge was initially identifying canvas objects for platform-independent automation. |
I am not really using the solution during development, however, for regression and automatic regression tests, I am using it. I use it to do visual Qt, which focuses on the GUI part of the application.
I can perform Java SWT. Additionally, I have been addressing testing issues. It's more focused on whether it will be fast. For the parts that have been automated in Qt, not everything is suitable for automation.
There is nothing you can do for almost every application. If you do it for a single version, it is rather easy. However, if you want to run it for different versions of the software, then you need the Qt version of Java. You need to set up some special environment variables to be able to do that.
I have been using it for four years.
It is very stable.
Qt scalability will depend on the number of classes I have. With one license, just one user or one test scenario can be run at a time.
Support isn't always helpful. I sometimes need to find solutions myself.
I am using what you mean. It was Mercury Interactive, and then it was HP. I am uncertain about the name exactly.
Once I know how to set it up, it's about setting up some environment variables, and then doing the install. Once I know how and have authorization, it is quite easy.
I have actually faced testing issues. It is more focused on whether it will be fast. For the part that has been automated in Qt, not everything is suitable for automation.
I'm aware of the price from three or four years ago, and it depends on the number of users. For the developer license, it is about $5200 a year.
There are some other teams currently investigating more tools in that area.
It depends on the licensing. It is scalable, I would say. The reason is that Qt supports testing on Java SWT, and HP probably did not. I conducted an evaluation, and at that moment, Qt was the best.
The overall product rating is eight out of ten.
We use Qt Squish primarily for test automation in our embedded systems. While I configure it and set it up, another person uses it for testing. We also use Squish integrated with Qt, a framework for the user interface, which is a crucial feature for us.
Squish allows us to automate testing in our systems, which is essential for dealing with complex applications.
Squish is integrated with Qt, which enables us to test the user interface effectively. Also, the BBC feature allows us to define tests by giving each step a name and parameters, building tests using building blocks.
We encountered issues with the embedded environment and building for the Qt version. Upgrading Qt and Squish can be annoying and would be better if Squish were more integrated with Qt, to ease the upgrade process.
I started using Squish in 2012, used it for a few years, paused, and then resumed about a year ago.
Qt Squish provides enough features to create stable tests. However, the stability can depend on how the tests are defined.
Unstable tests can occur, particularly when using features like 'Snooze'. Squish as a company has been stable over the years, which is important for us.
We are satisfied with the scalability of Squish for our purposes. It appears that the developers have thought about scalability, and it is suitable for our medium-sized company.
Our experience with support has been mostly negative. We haven't received useful answers from the support team, despite paying for it and having meetings.
Positive
My role involves Squish integrated with Qt. Qt bought Squish, making it a part of their toolset.
Setting up Squish required more configuration to figure out how it needed to be implemented with our system. However, installation can be automated.
We don't have specific technicians. The setup and configuration are performed by developers and testers.
Qt and Squish are considered to be on the expensive side compared to other software development tools. The pricing is not very flexible, which has been noted as a concern.
I'd rate the solution nine out of ten.
We use Squish to test real time traffic control screens
Automated testing has clearly some advantages
I like the dashboard. It's virtual, and you can see the customer results. I can do it at night and in the morning. I think it also automatically emails results.
The price could be better.
froglogic Squish is a scalable solution for functional testing
(not made for performance/load testing
I used HP before froglogic Squish. I made the switch because my colleagues studied it and recommended it.
The setup itself is straightforward, but you need to read the documentation thoroughly before setting it up more complex solutions. Using (SQUISH FOR WEB and SQUISH For JAVA at the same time) Or, testing different versions of JAVA requires a more complex setup.
I didn't set up the original (simple) solution, but I have installed many new versions and adjusted some scripts (environment variables) so that I can be used to run different versions (WEB and JAVA) at the same time. and for Java Running different versions in Parallel --- Each Requiring a different SQUISH Server
I would recommend this solution to new users.
On a scale from one to ten, I would give froglogic Squish an eight.
My primary use case for this solution is for automatic software testing. Specifically, I use it to test software's user interfaces using a test tool that automates these tests.
The product's most valuable feature is its modular framework, which allows for creating testing frameworks and functions adaptable to different user interface objects and libraries, such as Windows Presentation Foundation, the QT Library, and Web interfaces. Its platform independence is a significant advantage.
The platform could be improved by implementing some basic functionalities that are frequently used, such as login procedures and screen handling when multiple screens are used at the workplace.
I have been using froglogic Squish for two and a half years.
We have 18 Squish users in our organization. Because of the floating license, it is a scalable product, and we can easily increase the license number.
The technical support services are quite fast and effective.
The initial setup process is straightforward. However, I have encountered some things that could be improved during the process, particularly when reinstalling the software. These errors occur mainly during the uninstallation and reinstallation steps. The version that I'm using is installed locally on computers and a server. It operates under a floating license model, allowing flexibility in its deployment and usage.
One of my colleagues takes care of the deployment and maintenance of the platform.
The platform is highly-priced.
HMI testing with Squish is similar to testing normal software because both involve graphical user interfaces. The experience is largely the same. However, HMI systems are typically easier to test because their interfaces are usually more straightforward and less complex than other software, such as complex 3D applications. This simpler structure of HMI interfaces generally makes the testing process smoother and more manageable.
Integrating behavior-driven development (BDD) within Squish is particularly beneficial in terms of enhancing testing efficiency. This feature allows for the creation of readable test descriptions or designs using BDD principles. It lets users write clear and understandable tests initially and then incrementally implement the necessary functions in programming code.
The behavior-driven approach encourages the creation of reusable and well-structured test steps. When you carefully create the test scenarios, it becomes much easier to avoid writing unnecessary code, enhancing the reusability of the tests.
I am very satisfied with how the product handles desktop and embedded HMI testing. I appreciate its stability and wide range of functions, which allow it to tackle various testing challenges effectively. It is a powerful and reliable testing tool, but it is also expensive.
I recommend Squish for automated GUI testing, provided the user has the necessary budget. I rate it an eight out of ten.
I use Froglogic Squish for desktop UI testing.
I find it very user-friendly and easy to start working with. The main benefit for me is that it allows testing applications developed in the Qt language. This capability makes Squish a game-changer, as it's the only tool I've found that enables automation for applications written in Qt.
I appreciate three main aspects. Firstly, the documentation is excellent. Secondly, I value the way the tool efficiently locates elements during testing. These are the two aspects I particularly like.
I'm relatively new to Squish, so I'm not familiar with all its pros and cons. Currently, I haven't identified any specific improvements. However, one feature I miss is Git integration within the tool. In my previous experience with Selenium and Python in PyCharm, it was straightforward to create and review changes before pushing them. I haven't found a similar option in Squish, and having an integrated tool for managing conflicts would be beneficial in certain scenarios where collaboration is involved.
I have just started working for a couple of months with this solution.
It's stable.
As I mentioned earlier, we haven't completed the full cycle yet. However, based on what I know, defining test modules for remote machines and generating reports seemed straightforward. In the direct desktop version, it was easy to set up and execute tests on remote machines, with reports automatically generated and sent via email without much configuration. However, I currently face challenges executing tests on remote machines and generating reports in the Squish GUI Tester.
The process was straightforward for me. However, I haven't completed the full cycle with a remote machine yet. Currently, I'm using it locally on my PC, and it's working well in this context.
Actually, we use a device floating license, which means it's only for one user—either me or my team lead at this point. As for maintenance, there are some pros and cons, but overall, it's manageable. We've established procedures for working and maintaining the code, and I don't find it particularly difficult.
At this point, it's too early to provide a definitive assessment of Squish. However, I believe any tool that can automate processes is valuable and will likely yield a return on investment in the future. Currently, I cannot provide detailed insights, but I anticipate its worthiness in the long run.
It's quite expensive.
Certainly, I would recommend Squish. I would rate it around eight to nine.
froglogic Squish is a tool used for GUI regression testing.
If any of our clients have a particular GUI and they want to do a GUI regression testing or fully automated testing and specifically have the framework, such as Qt, then this solution is a unique solution for that use case.
This is a great tool to achieve automation for GUI regression testing. This has really reduced the entire release cycle time.
froglogic Squish is one of the most desired solutions if you have Qt as a framework and if you are looking at GUI regression testing. froglogic is a part of Qt as a company.
Earlier, Qt and froglogic were technical partners, but now froglogic as a company has been taken over by Qt. For anyone who is working on the Qt framework and would like to perform a GUI regression, froglogic Squish should be the product for them to use. It is seamless in functionality and with the operating system. If you're working on a Windows or Linux environment it works well for both environments.
There had been a lot of improvements with froglogic Squish already. There were some scenarios in which this particular solution was available in different flavors. They have pulled everything together in one solution. There were some monitoring systems, which were missing out from the solution earlier. They have a centralized dashboard for monitoring the test cases and their execution. It's a full-blown solution, there are not many glitches in terms of something missing out of the package.
The froglogic Squish solution is only handling GUI regression testing, this is its forte. However, a lot of clients are looking into performance testing associated with it. If a performance testing capability can be added as a part of it, this would bring great value. froglogic Squish has a code coverage solution and they have done a pretty good job on it. The penetration testing could be added as a separate module, this would be beneficial.
I have been using Squish - now a QT company product for almost 8 years
froglogic Squish has been in the market for a long time and it is stable. They do not have too many releases which can have drawn backs. When they release an update there are not any problems with them.
The scalability of froglogic Squish is good enough. There were certain image recognition scenarios, in which we had a glitch.
I would rate the scalability of froglogic Squish a four out of five.
The Technical support of froglogic Squish is excellent. I'm a part of that team directly, and I can tell you that there's no problem with their abilities.
I rate the technical support offered by froglogic Squish a five out of five.
froglogic Squish is a very simple solution to implement. It is a plug-and-play solution. The solution does not have a complicated implementation it is easy.
froglogic Squish does not have a lot of competition. If somebody is specifically working in a Qt environment and they're looking for a GUI regression, this is one of the tools that they have to look into.
It's recommended not only by Qt, but it is also one of the best available tools in the market.
I would rate froglogic Squish a nine out of ten.
We are customers of Froglogic and I'm an automation quality assurance engineer.
This product can work with QT applications and cross-cut from them, both on Windows OS and on MAC, as well as on mobile operation systems like iOS and Android too. The other value to this product is that it is an all-in-one feature. It has an IDE for developing and debugging, inspector, utilities squishrunner to run test suites and squishserver to connect to AUT via cli.
I'm not completely satisfied because although the ID is good, it could be improved with suggestions of names for some method, for example, or variable, or class. I'd like to see suggestions for options. I'd also like the solution to be faster because a project is initially saved quickly, but after an hour of working, saving takes longer and I need to reload IDE and turn all of them on to improve speed.
They could have better support for scheduling jobs in Jenkins. As things stand, continuous integration is very poor, and when you work in production you need many more settings in order to tune it, to be a Web user interface, for example, which is currently impossible. And there are just a few basics I think you can manage in Jenkins, because Froglogic made some plug-in to Jenkins that connects Squish and Jenkins, but the plug-in is not as good as expected, and should be improved.
I've been using this solution for 18 months.
The product is quite stable, I've only had a few crashes.
I believe that the solution is scalable, because in the latest version of Squish, they started a new feature working in a network. I haven't tested it yet but I believe it's scalable. For now, I'm really the only one in the company using the product.
I think the licensing price is okay. I believe for one person, the cost is around 2,000 Euros. That's the initial cost, after that you buy support and it cost 800 Euros, which is much lower, It's a one-off purchase but without support you miss the updates.
I rate this solution an eight out of 10.
Table-driven testing is our main case. Using Squish, we are able to do table-driven testing very easily. Drive your scripts with data from a variety of data sources such as CSV, TXT, TSV, MS Excel, Databases. One more best thing to mention would be the capability of behavior-driven development testing. Squish uses Gherkin Syntax which is a standard BDD language. Squish can be easily integrated with ALM, continuous integration, build integration, HP Quality Center/HP ALM, Microsoft Visual Studio/TFS/MTM integration, Rational Quality Manager, Seapine, TCM integration, Maven, Ant, TeamCity, Bamboo, Jenkins/Hudson.
Squish is very good in handling hybrid applications. We can perform behavior-driven development(BDD) in Squish very easily.
Squish has introduced one new feature which we are waiting from long time i.e., OCR(Optical Character Recognition) Support.
Previously, for doing table-driven testing, we had to do a lot of circus. Using Squish, we are able to do table-driven testing easily via a straight forward process. We have automated the entire process of running scripts, and Squish will never be stuck. Squish's data-driven testing is very powerful, so it will never be stuck if the size of data is too heavy.
The Squish team provides regular updates, and they are improving the features of Squish. Anyhow, we can't automate the applications which are completely built on C/C++ without using Qt. As per my view, Squish should provide support for these type of applications.
Yes, we've used different tools which we didn't find much powerful as that of Squish.
The setup is straightforward, it is a medium cost tool. It has two types of license, i.e., fixed and group licenses.
Yes, I have evaluated a few more tools, but I can't reveal the names of the tools.
My application includes Qt and Java objects that run on Windows and Linux operating systems. We wanted to perform automated GUI regression testing based on objects so that the same test script can be used in different machines. Our intention is to run regression tests automatically using CI (Jenkins) or scripts. We were looking for a tool that is user-friendly, and test scripts should be created in almost all well-known scripting languages. Squish helped us here.
We were struggling to create object-based test cases for hybrid applications. Squish saved our time and money by creating reusable operating system independent test scripts. This helped us to automate the test run using CI (Jenkins) and scripts..
Robotics automation could be added with Squish. Squish works based on objects so, adding this feature would actually help us a lot to get everything in one suite. Their roadmap shows robotic automation and local web portal based reporting will be added in future releases. If this can be fastened, that would be really helpful.
Squish is a very stable product, and it produces stable results as it is working based on objects.
Squish covers almost all the features of automated GUI regression testing.
Customer support of Squish will work out of the box. Squish's support team will give you the best technical support and friendly customer service.
Yes, we have used multiple open source tools before Squish. The main problem with open source tools and some commercial tools are that they work based on visuals and pixels but Squish on the other hand works based on objects. So, Squish results are consistent and reusable.
Squish test scripts can be created in multiple scripting languages, and the execution can be automated. Squish results can be exported in HTML and XML.
Squish results can be pushed directly to Jira.
The initial setup was very simple. We have completed the entire setup and first run within five minutes.
Implementation was simple and straightforward. Still, if you need to get help, the Squish team gives professional support even at the evaluation stage. They do have local technical partners to fasten the support.
We are getting the value of the product even now. Squish gives perceptual licenses, so the ROI of Squish is very satisfactory.
The setup of Squish is very simple; it starts with installing the installer (executable file).
Cost should not be a problem if it is justifiable by the tool, I believe. Squish has a simple licensing model (single users and group license).
Yes, we have evaluated multiple open source tools and some commercial tools as well.
Squish requires the executable application and not the source code. So using Squish will be simple, and I am sure anybody can handle Squish very easily. Squish provides free evaluation with professional support. I would say, take up an evaluation and try it on your application. Squish is the best GUI testing tool for me.
Using a mix of Squish editions, it is possible to fully automate the GUI tests of hybrid GUI applications such as a Qt application with embedded, native Windows controls or a web application which embedded Java applets or starts a Java Web Start application.
A variety of non-proprietary scripting languages are available when working with Squish. Select from Python, JavaScript, Ruby, Perl or Tcl, and take advantage of the world of knowledge at your fingertips in each of the scripting languages.
Each scripting language offers its own advantages, whether based on your existing knowledge of one or more of the languages, or by addressing a key test scenario using an existing and proven approach already available in the scripting language.
The behavior-driven development approach – BDD – centers around stories written in a “ubiquitous language” that describes the expected behavior of an application.
The use of the human-readable language Gherkin allows technical as well as non-technical project stakeholders to participate in the authoring of feature descriptions and therefore tests.
Those descriptions serve as a base for the work of both developers (specification and feature descriptions) and testers (test steps).
We have faced some difficulties in identifying canvas objects initially. Canvas images are not actual objects that can be picked by any inspect tool (including Squish as it works based on Objects). You need to use the visual picker or mouse click property of Squish to work with them. I have faced some difficulties in automating this for platform-independent automation. Once it got automated, then it is going fine.
Customer support was good. They work out of the box and are willing to add a new feature if we say and if it is feasible.
Installation was simple and straight forward (just a single EXE that has to be installed).
We were able to manage the installation by ourselves as it was simple and straightforward.
