This is a great tool to achieve automation for GUI regression testing. This has really reduced the entire release cycle time.

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.

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.

• 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

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 most important part is that it allows me to create black box tests faster and easier. Along with it's features for apps written in C++ QT, gives me even some inside about the code of the application under test.

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..

Now we have completely automated the Squish runs using CI tools and Squish is not at all getting stuck or creating any problem. Squish is running smoothly on these tools without any problem. Squish is very good in data-driven testing when we have bulk data.

Stable automation framework with it's own object library enabled us to move all of the tests to a Continuous Integration farm.

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.

It has eliminated the back-to-back work of writing the scripts again. I would just be calling a function or file for reusing. Squish has got some good wide range of plugins available to integrate with multiple tools. With Squish, we can do remote testing which is very easy and straightforward.

I have used froglogic Squish mostly for regression testing. Automated regression tests are run nightly and this helps us to find regression bugs quickly. The use of Squish also reduces test execution time.

It has helped for building automation frameworks for multiple products and also have used the tool for cross platform products like integrating Qt and web based automation.

We were able to automate testing process for a big project, otherwise we have to lost such ability.