Squish tip of the week: How to know what code your testing actually exercises

Did you know Squish GUI Tester and Squish Coco can work together to reveal more about your testing?

Integrate your testing with Squish Coco to answer these questions:
  • How many of our tests are redundant?
  • What areas of our application are the tests not reaching?
  • If I only had a given amount of time to execute as many tests as possible, which tests would you choose?
  • …?


Squish tip of the week: Update a changed object in the Object Map

Changed Object?   No Problem!

Squish can help you update objects in your Object Map

Here’s How:
  1. Locate the item to update in the Object Map
  1. Manually navigate the Object Map for object
  2. Right-click object’s Symbolic Name in script and select Open Symbolic Name


Squish tip of the week: Creating an automated test from a manual test

As you begin building your Automated GUI Testing Framework, the first set of tests you’re likely to automate are those manual test cases which while required are perhaps mundane, repetitive or require meticulous detail review.

Use existing manual test cases as your base

Sample Manual Test Case: Create New Address Book
  1. Open Application
  2. Create a new address book using application menus
  3. Expected result: Confirm new addressbook created without any entries


Squish tip of the week: How to find and use dynamic objects

Squish provides many options when working with dynamic objects:

  • Using Wildcards in the Object Map
  • Using Regular Expressions in the Object Map
  • Using Wildcards or Regular Expressions with Object Real Names in a script
  • Building Object Real Names within a script using information retrieved during script execution

Watch the videos below to learn two approaches to working with dynamic objects

The videos demonstrate the Squish for Qt edition and sample Qt application; however the same options apply working with other Squish editions.


Squish tip of the week: Generate data-driven script from data file

Did you know Squish can help you create a data-driven script?

Simply highlight the code to loop, right-click and select Make Code Data Driven. By telling Squish which data file to use, Squish will produce the loop and applicable variable statements to extract the data from the data file.

Learn more by watching this quick video tutorial


Squish tip of the week: Create tests against a remote environment

Your batch runs, or scheduled automated test executions can run remotely without question. But did you know you can also develop and manage tests remotely?

With the Squish Server running on the remote environment, the Squish IDE can create and execute tests remotely (you still need the ability to control the remote AUT, via remote desktop, vnc, direct access to the system, etc.)

Three simple steps:
  1. Indicate what incoming IP addresses to allow by modifying the squishserverrc file on the remote machine.
  2. Start the Squish Server on the remote machine to listen for incoming requests
  3. Point the Squish IDE to the remote machine’s IP address and port from Edit > Preferences (Mac: Squish > Preferences) > Squish > Remote Testing



Squish tip of the week: Building a script toolbox

A different twist on the tip this week. We want to hear from you!

What are your most value added ‘toolbox’ scripts?

Implementing an automated test framework with re-usability in mind saves time down the road, especially when it comes to script maintenance. Each application should have a toolbox of re-usable scripts.

Squish tip of the week: How to work with an already running application

Question: Is it possible for Squish to hook into (interact with) an application that was started manually?

Answer: Absolutely!

Here’s how

  1. Start the application using start*aut instead of starting it directly:
    startaut --port=<portNumber> <AUT_PATH>
  2. Register the AUT as an Attachable AUT

Going Forward

Using start*aut you can playback or interact with a running application using Squish, because the hook is already loaded and ready.

  • Update your Test Suite Setting’s Application list to use <No Application>
  • Now when you record, the Record Settings window displays where you can select to use the running application