The ability to go through a test sequence and have Squish record the steps and verify the expected results. Then the sequence is saved and a test can be run quickly to see if any test is violated.
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.


| Author info | Rating | Review Summary |
|---|---|---|
| Contract Programmer at a non-profit with 51-200 employees | 4.5 | Squish significantly improved my testing, recording steps and verifying results effectively, bringing organization to our process. My main suggestion is for Squish to display assigned GUI feature names, not just generic ones, to streamline use. |
The ability to go through a test sequence and have Squish record the steps and verify the expected results. Then the sequence is saved and a test can be run quickly to see if any test is violated.
Having any test system, especially Squish, dictates a philosophy of testing that organizes one's outlook into a viable manor of testing. Our previous, haphazard approach to testing was not effective. Using Squish has led us into an organized mode of testing.
We had means of verifying that a client record was properly defined, but we did not test to see that all of the information for that client was removed if and when the client was deleted. The Squish discipline led us into resolving this discrepancy.
NetBeans is a Java Integrated Development Environment (IDE) particularly well suited for Graphics User Interface (GUI) development. It allows a number of GUI features such as Text Field to be defined and positioned in a GUI window. When they are first placed in the window they are given generic names such as "textfield1". Then the developer is allowed to change the name of the feature to, e.g. "ClientName", which is easier to remember the association with a program object.
When Squish is running it allows the developer to place restrictions on the contents of GUI features in order to verify correct functioning of the GUI program. These are mostly referred to by the generic name rather than to an assigned proper feature name. This requires the Squish user to either keep a cross reference list of feature names for each GUI window or to try to discern the proper feature from its contents. It would make the work of the Squish user easier and quicker if Squish would display the proper feature names, when assigned.
We have used Squish for about 9 months.
No issues in deployment.
Squish was found to be very stable, no crashes.
We did not have an issue with scalability.
Customer Service was always timely responsive and competent
Technical Support:I did not have an issue with technical support.
This is our first experience with test automation. We knew that what we were doing did not work. Squish is a rational approach to testing of software.
No problem in initial setup. The document ion is well prepared. But one has to realize that testing of a software system, especially a GUI, is a difficult issue. But the results of not adequate testing is a nightmare. So effort in the preparation of testing methods is well spent.
We prepared our testing system in-house.
We are a charitable organization. Our ROI is infinite.
We have found Froglogic to be a very equitable organization to deal with.
We did not find another option that had the parameter that we were looking for.
I believe that testing of software systems (especially GUI) is a difficult issue--some people believe that if the software is written correctly you don't have to worry about it. I believe that is true, but that software is never written correctly at first. There are errors in coding. There are errors in the specifications. There are changes that are necessitated as the system is placed into use. Testing to verify that the system is performing as all expect it to perform is a huge task, similar to the original coding of the system. My advice is to take software verification very seriously.
| Product | Mindshare (%) |
|---|---|
| Qt Squish | 2.2% |
| Tricentis Tosca | 10.5% |
| OpenText Functional Testing | 8.5% |
| Other | 78.8% |
| Company Size | Count |
|---|---|
| Small Business | 8 |
| Midsize Enterprise | 2 |
| Large Enterprise | 7 |
| Company Size | Count |
|---|---|
| Small Business | 208 |
| Midsize Enterprise | 74 |
| Large Enterprise | 223 |
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