Qt Squish Reviews

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.

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.

We use Squish to test real time traffic control screens

Automated testing has clearly some advantages

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.

• We used it for two projects, one was developed using smart GWT toolkit and other used flex
• Locators kept changing in GWT for every build
• For flex all the other solutions required the code to be build using custom parameters and libraries
• Froglogic provided us a solution which supported both the platforms, and no need to build code with vendor provided custom libraries

• Ease of use
• Integration with Rational Quality Manager
• Support for wide range of tool kits (HTML, GWT, Smart GWT, Flex)
• Tech Support of Froglogic is awesome, you talk/chat/mail directly to the designers/developers of the product.

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.

The most important thing with an automated GUI testing tool is the ability to quickly and accurately identify the UI components you want to script up.

Squish, after evaluating quite a few alternatives, was the best at doing this (we have a C#/WPF application).

Another feature, which has been the best for us, is the fact that once UI components are mapped, all testing can be performed via scripting languages.

When I was working as a developer in test, I wrote an entire GUI testing framework in JavaScript which was possible because of Squish’s ability to map the UI components accurately.

Squish was also easily integrated into our CI system (TeamCity). It had native support for TeamCity and allowed a Squish build step to be created that can run all, or a selection of automated tests. So now, when we have a successful build, all our UI tests are ran on the products which gives product management and the team greater confidence.

My company began investigating automated GUI testing because it was something that we did not do at all and the manual testing overhead meant that we were spending more and more time regression testing our products prior to a release.

Now we are using Squish to automate our user stories as they are implemented, therefore removing the need for a regression phase at the end of a release. This frees up our QA team to perform more exploratory testing instead of repeating regression scripts.

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.