Packet Design QA Success with Squish

Packet Design LogoSilicon Valley based Packet Design develops networking route and traffic analysis solutions. Their quality assurance team have been using Squish for a couple of years, and for this Squish success story we had the pleasure of talking with Aj Alhait, Packet Design’s QA Manager.

froglogic: On which platforms is your software developed and tested?

Aj: Our application is developed on Unix and tested on Unix, Windows and Apple Mac OS X platforms.

froglogic: How did you learn about Squish?

Aj: The developers who selected Qt as a development environment for our application recommended Squish to me, and that led me to evaluate it for our QA needs.

froglogic: When did you start using Squish?

Aj: We started to use Squish productively about two years ago.

froglogic: What are the main reasons you decided to use Squish for your automated GUI tests?

Aj: The three most important reasons that persuaded us to choose Squish were its

  • cross-platform support;
  • support for multiple scripting languages (Editor’s note: Python, JavaScript, Perl, and Tcl);
  • dedicated support for Trolltech’s (now Nokia Qt Software’s) C++/Qt GUI toolkit.

froglogic: Why did you choose Squish rather than a competing tool?

Aj: From our point of view there was no serious competition. There was only one other testing tool that supports Qt based GUIs and Squish has a much richer feature set and was a much better fit for our needs.

froglogic: What’s your favorite Squish feature?

Aj: Its compatibility with HP Quality Center. This allows us to automate our Squish tests runs using HP’s Quality Center, which is very convenient and saves a lot of time.

froglogic: Are you satisfied with froglogic’s technical support service?

Aj: Yes, froglogic’s support support service has proved to be very good.

froglogic: How many Squish tests cases do you have at the moment?

Aj: We have about five hundred test cases automated with Squish at the moment.

froglogic: Where do you see the main benefit of automated testing?

Aj: Primarily to help ensure that new versions of our application don’t introduce regressions. We can’t keep manually testing the same features over and over for each new version to find regressions—there isn’t enough time for that. So we had to automate testing those features to automatically find regressions as early as possible.

froglogic: Do you use any other third party or internal tools as part of your testing effort?

Aj: Together with Squish we also use HP Quality Center, some Tcl scripts, and Ixia.

froglogic: Aj, thanks for your time, and we are looking forward to continuing to work with you in the future.

Aj: Keep up the good work and best wishes for your success and growth! We are always happy to see good tools become available for the software testing industry.