Qt Squish Reviews

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.

• Its remote testing is powerful and very interesting to perform for those who want to do testing in a different machine. 
• Table-driven testing is one more excellent feature which I believe is most useful for those who want to check bulk data which is in CSV, TSV, and so on. 
• Its record and replay are very powerful wherein Squish will not miss any action. 

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.

It supports many platforms, which helps in getting automation solutions for most of the complex UI products.

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.

It still requires better solutions for object identification and an enhancement to identify all the objects of the AUT before building the object map.

I've been using it for three years.

There have been no issues with the deployment.

There have no issues with the stability.

There have been no issues scaling it.

It's 7/0 - they're good a providing fixes and patches, but the video support is expensive.

We switched to frogLogic Squish because it supports multiple scripting languages.

The initial set-up is very straightforward. Complexity lies in integrating the squish binaries with QT code

The only hindrance of using it for multiple platforms or languages is it comes with different licenses for each flavour.

It's an easy to learn tool. And it has all the UI automation solutions. Can be easily integrated with applications like ALM.

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

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.