Qt Squish Reviews

• Object Map & Object Identification Tools - This feature simplifies test creation, test maintenance and troubleshooting. With this feature I can produce stable test scripts
• Powerful and intuitive Integrated Development Environment (IDE) - I use this IDE daily for creating new tests, debugging tests and running tests. Squish IDE has been very easy to use.

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.

Recording tests with Squish IDE creates quite ugly code and it is very difficult to maintain tests that have been recorded. That is one reason why I haven’t used Recording and Playpack feature at all.

I haven't encountered any issues with deployment.

I haven't encountered any stability issues.

It's scaled as needed for us.

Be patient and study product. Use the scripting language which is most familiar to you. Don’t hesitate to connect Squish customer support.

The most valuable feature is python compatibility.

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

I like it how it is, but it's not cheap.

I've used it for two years, starting with v4.

There were no issues with deployment.

There were no issues with the stability.

There were no issues with the scalability.

Great ! It is not cheap, but they are quick in providing you assistance, creating a patch or noting a feature request.

Great! It is not cheap, but they are quick in providing you assistance, creating a patch or noting a feature request.

Not really, there aren't many automation tools available for OS X.

Initial set-up of product it self is easy, but there was a bit sweat to make it working with our product and setting up PoC. Froglogic Technical support played a great role in helping us to setup PoC

We implemented with team working on project where we applied the automation tool. It wasn't difficult but patience was required.

The ROI can be seen in reducing the need for two automation engineers and machines used locally prior to moving all of tests to CI farm.

This is what you would like if you are looking for for continues integration and continues delivery, a must have tool for Agile process.

Rich availability to recognize Qt controls – other tools do not provide such support – it was most priority. Also picture verification with masks/threshold – because our AUT has 3D graphics.

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

I used it for two years, then I transferred my knowledge with the tool to other project members.

Sometimes, I had problems, but their support team resolved almost of them in short time.

It high rate as they really do their best. For example, they sent me a new package with fixed build within a two to four hours.

I have used HP QTP, Rational Robot, MS VS Coded UI Test, and Selenium.

It’s quite easy – unzip, some settings and go ahead.

I implemented in-house solution that based-on my experience, approaches. Sometimes I used vendor team’s help as a snipped.

I did not calculate the exact ROI, but within half a year automated test coverage was about 50% - it’s а good value

If you are looking for simple, not expensive, with nice support and for Qt-application tool – I think, it’s the best one. The tool provides a few script programming languages for selection.

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.

The only criticism I have is the IDE needed a bit of polish in version 5.2 (this may have been fixed in the latest versions). For example, I had a few occasions where Squish would fail to hit breakpoints. An application restart would fix this however.

I've used it for approximately 12 months.

Customer service at froglogic is very good. They answered most support emails within about an hour. They were also happy to provide engineering builds if they had a fix to a problem that was not in a released version yet. They also make themselves very available if you need a call with a representative to explain new features etc.

This was our first UI automation tool but we did evaluate others. We chose Squish because of its scripting ability, instead of just recording a test. Also it was the best tool for UI component identification in our product.

Installation is via a self-extracting exe. Getting up and running is very simple, start the IDE, pick your scripting language, point the Application Under Test at your products .exe file and you can start working.  For our build agents, installation is the same and the TeamCity integration handled the set-up.

We implemented in-house. No problems at all in getting our workflow up and running. Any problems that may be encountered will be diligently handled by Frog Logic support.

The biggest ROI is the time that we got back from our QA team because they didn’t have to manually regression test our product every release. They can now concentrate on exploratory testing and doing what a QA engineer should be doing, not just following manual test scripts.

It also means that, because we no longer require a regression phase in a release cycle, we are releasable at any time in the true agile sense. As long as our build system is green, we’re good to go.

For licencing, we purchased an unlimited licence that can be used on as many machines as we like with no restrictions.