Qt Squish Reviews

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

• Features like recovery scenarios can be added as an improvement
• Reporting can be improved.

It worked great, did parallel executions, and distributed executions.

Nope

Customer Service:

10/10

Technical Support:

10/10

We were using HP QTP, before selecting squish we did a POC on TestComplete and some other vendor tools. Cost and non availability of Support for new tool kits were the reason we moved to Squish.

It is a simple tool. Anyone with a fair background in automation tools can achieve setup and start creating suites in no time.

Licence servers were implemented by the vendor team. Implementation, understanding the tool, creating proof of concept was done by me.

Stable automation suites.

All combined, we had a total of 900 scripts divided into different regression suites which we ran couple of times every week for regression on development and pre prod environments.

Execution was triggered from Rational Quality Manager and scripts executed on three of our local machines running Squish adapter.

It definitely reduced the overall testing time.

HP QTP

TestComplete

Stable automation suites, it is cheaper than most of other vendor automation tools, it supports wide range of tool-kits, even embedded solutions, one tool for all your products. The tool itself comes with a simple help, just go through it. If you still face issues, drop a mail to support and all your issues will disappear.

Using a mix of Squish editions, it is possible to fully automate the GUI tests of hybrid GUI applications such as a Qt application with embedded, native Windows controls or a web application which embedded Java applets or starts a Java Web Start application.

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 behavior-driven development approach – BDD – centers around stories written in a “ubiquitous language” that describes the expected behavior of an application. 

The use of the human-readable language Gherkin allows technical as well as non-technical project stakeholders to participate in the authoring of feature descriptions and therefore tests. 

Those descriptions serve as a base for the work of both developers (specification and feature descriptions) and testers (test steps).

We have faced some difficulties in identifying canvas objects initially. Canvas images are not actual objects that can be picked by any inspect tool (including Squish as it works based on Objects). You need to use the visual picker or mouse click property of Squish to work with them. I have faced some difficulties in automating this for platform-independent automation. Once it got automated, then it is going fine.

Customer support was good. They work out of the box and are willing to add a new feature if we say and if it is feasible. 

Installation was simple and straight forward (just a single EXE that has to be installed).  

We were able to manage the installation by ourselves as it was simple and straightforward.

One of the most valuable features is the auto-completion of the code while you register your actions/clicks inside the application under test.

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.

The most complete way of testing is on several OS's, even platforms. Here, the solution provided by Squish, trough several python script files, could be simplified in such a way, so that even black box testers could manage it easy. At the moment, you need to have a basic knowledge about Python and programming so you can master it and use it.

I've used it for two years.

There were no issues with the deployment.

There have been no issues with the stability.

There have been no issues with the scalability.

I had several emails exchanges with the Squish support department. They know their product, and indeed they can provide solutions for your problems. Appeal to them with confidence.

I didn't use any other solution. Some other colleagues did an evaluation of several tools, and this was the closest to our needs.

Initial set-up is quite easy, because their package comes in the form of a binary for Windows. Now, after using it for quite a while, it seems logical and quite easy.

I need to give a minus to the the product, because the technical documentation, again, is not easy to understand if you aren't at least a basic programmer. Indeed, Squish sustains sessions of on-line training, that can really help a beginner, but still, you also need to have a minimum level of principles about programming.

This product was already implemented at a basic level, when I started using it.

Yes, other found solution was the one provided by Smart Bear. But we choose Squish, because it's more flexible and intuitive.

Some of you may find the Squish product easy to use, some of you may find it hard. I think that what's important in the the end is that the used tool to allow you to obtain the wanted result. This product, until now, allowed me to do this.

My application includes Qt and Java objects that run on Windows and Linux operating systems. We wanted to perform automated GUI regression testing based on objects so that the same test script can be used in different machines. Our intention is to run regression tests automatically using CI (Jenkins) or scripts. We were looking for a tool that is user-friendly, and test scripts should be created in almost all well-known scripting languages. Squish helped us here.

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

• In-depth support for all major GUI technologies
• Full support for all desktop, mobile, web, and embedded platforms
• Test script recording
• Automated test script creation on almost all well-known scripting languages like Python, JavaScript, Perl, Tcl, Ruby, etc.
• Powerful and reliable object identification and verifications
• No dependency on screenshots or visual appearance
• Powerful integrated development environment (IDE)
• A wide range of popular script languages for test scripting
• Full support for behavior-driven development (BDD)
• Full control via command line tools
• Integrations into test management and CI systems.

Robotics automation could be added with Squish. Squish works based on objects so, adding this feature would actually help us a lot to get everything in one suite. Their roadmap shows robotic automation and local web portal based reporting will be added in future releases. If this can be fastened, that would be really helpful.

Squish is a very stable product, and it produces stable results as it is working based on objects.

Squish covers almost all the features of automated GUI regression testing.

Customer support of Squish will work out of the box. Squish's support team will give you the best technical support and friendly customer service.

Yes, we have used multiple open source tools before Squish. The main problem with open source tools and some commercial tools are that they work based on visuals and pixels but Squish on the other hand works based on objects. So, Squish results are consistent and reusable. 

Squish test scripts can be created in multiple scripting languages, and the execution can be automated. Squish results can be exported in HTML and XML.

Squish results can be pushed directly to Jira.

The initial setup was very simple. We have completed the entire setup and first run within five minutes.

Implementation was simple and straightforward. Still, if you need to get help, the Squish team gives professional support even at the evaluation stage. They do have local technical partners to fasten the support.

We are getting the value of the product even now. Squish gives perceptual licenses, so the ROI of Squish is very satisfactory.

The setup of Squish is very simple; it starts with installing the installer (executable file). 

Cost should not be a problem if it is justifiable by the tool, I believe. Squish has a simple licensing model (single users and group license). 

Yes, we have evaluated multiple open source tools and some commercial tools as well.

Squish requires the executable application and not the source code. So using Squish will be simple, and I am sure anybody can handle Squish very easily. Squish provides free evaluation with professional support. I would say, take up an evaluation and try it on your application. Squish is the best GUI testing tool for me.

Our main test case is to automate the entire thing either to CI/CD tools. I have looked for a lot of tools on this, but we used to encounter one problem or the other. But with Squish, I didn't get many problems, and this is a straightforward procedure. One more use case is we will be using a lot of data like Database, CSV, TSV and so on. So, Squish data-driven testing is very powerful and easy.

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.

• Its powerful engine for record and replay of test cases
• It has a vast number of plugins for integrating with multiple tools.
• Squish tool documentation is so clear that each and every step is explained using some screenshots which will be helpful for new users and they can do everything.

Till now I have not noticed anything that needs improvement. I believe Squish is going at a great pace and in a good way. Squish is lagging in handling swing objects, but I believe Squish will overcome this shortly. Moreover, we don't concentrate on swing objects that's why I am not mentioning it as an important thing.

I have used some other tools, but when compared I feel Squish has very good potential.

Setup is straightforward.

Licensing is of two types, i.e., named and group license.

Yes. But I can't reveal the names of the tools.

Best tool, and a must-try tool for everyone.

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.

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.

Squish is very good in distributed batch testing. It allows to execute sets of script or batches and review the detailed logging and execution of results. Even we can use the test scripts for multiple test cases, i.e., global scripts which will be very useful for one who often uses the same script.

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.

Its remote testing capabilities are very good and powerful. Squish reusability of scripts is an easy and good feature. Squish data-driven testing is very powerful and we can easily check for bulk and huge data without any issues.

Not much as of now. Squish is going in a good direction and if I feel any difficulty or anything needed to be improved, I will let you know.

We previously used an open source tool.

Setup is straightforward, and pricing is medium.

Licensing is of two types:

• Named license
• Group license.

Squish was my first tool to evaluate and I felt Squish met our requirements.