Squish tip of the week: Determine patch regression risk

What if you could determine the impact of a patch on your application?

  • Do you know which tests, if any, validate the impacted code?
  • How about what code or functions were introduced and and require new tests?

Squish Coco’s Patch Analysis report can tell you that and more


You’ve applied a patch to your application. Now you want to know the potential impact of that test on the stability of your application.

In the prior version of your product you ran your tests (unit, automated, manual, etc.) against your instrumented application (application built with Squish Coco instrumentation enabled).

Now with the patch applied, simply run a diff on the two application versions, and using the diff result, Squish Coco’s Patch File Analysis report reveals:

  • Source code impacted by the modification
  • Which tests cover the impacted code
  • Source code impacted where no tests exist
  • New source code for which tests are needed
  • and more

Assess the risk for potential regressions – what to retest – where new tests are necessary – the impact on your release plan

Snippets from a Sample Report

Overview Statistics

click to zoom

Source Coverage Details

click to zoom

More Information

Squish tip of the week: Reuse script functions in BDD tests

With the introduction of BDD support, all the existing scripts aren’t lost – quite the contrary – existing scripts and functions still work as always, and now those functions can also be called by BDD tests.

Consider the following Test Suite Resource functions:

def invokeMenuItem(menu, item):
    activateItem(waitForObjectItem(":AB_QMenuBar", menu))
    activateItem(waitForObjectItem("{type='QMenu' \
    title='%s'}" % menu, item))
def addNameAndAddress(nameAndAddress):
    invokeMenuItem("Edit", "Add...")
    for fieldName, text in zip(("Forename", "Surname", \
                    "Email", "Phone"), nameAndAddress):
        type(waitForObject(":%s:_QLineEdit" % fieldName)\
             , text)

def checkNameAndAddress(record):    
    table = waitForObject(":Address Book_QTableWidget")
    for column in range(len(record)):
        test.compare(table.item(0, column).text(),


Squish Coco 3.3 Released – now with Patch Analysis

We are excited to announce the release of Squish Coco 3.3!

The new features of this release include Patch Analysis, speed improvements, updated reporting and more.

You can read the full announcement at http://www.froglogic.com/news-events/index.php?id=squish-coco-3.3.0.html.

We will also host a live webinar showcasing Squish Coco 3.3 on Tuesday, September 22nd. Register here.

We hope you take advantage of the new features and as always look forward to your feedback. For feedback, email squish@froglogic.com.

Squish tip of the week: Use grouping and filtering your Squish HTML reports

The new HTML reports in Squish 6.0 make pinpointing failures and drilling down into details much easier.

  • View a collection of reports from one or more test suites or executions
  • Tree-style navigation
  • Filter by Pass / Fail
  • Hide or display logs
  • Tool tip details on mouse over
  • Drill down to a single report
  • Pass percentage automatically calculated
  • Ability to group the pass / fail status of sections in a given test case

Try them out!

  1. Download this example report
  2. Or try it yourself using the –reportgen html option


click to zoom

Squish 6.0 with fully integrated BDD support released!

About two years after the release of Squish 5.0, we are proud and excited to make Squish 6.0 available to you.

The main new features of this release are fully integrated support for Behavior Driven Development and Testing (BDD) as well as major improvements to Squish’s reporting capabilities.

You can read the full announcement at http://www.froglogic.com/news-events/index.php?id=squish-6.0.0-released.html.

A quick video introduction to Squish 6.0 and BDD can be found at http://youtube.com/embed/62Vrnb21hio?vq=hd1080&autoplay=1&rel=0&showinfo=0&autohide=1.

We will also host a live webinar showcasing what’s new in Squish 6.0 on Wednesday, September 9th. Register here.

We hope you take advantage of the new features and as always look forward to your feedback. For feedback, email squish@froglogic.com.

Squish tip of the week: What to automate next? How to best expand your automated test suite

Once you’ve established an initial test framework – perhaps you even followed the Squish Tip of the Week: Where to start? – how do you determine where to continue expanding the automated test suite?

New features! Features not even in Development (yet).

  1. As a team, write the new feature in Gherkin. That becomes your initial test.
  2. Automate the feature (yes, even before it’s implemented – see diagram’s Writing a failing test step)
  3. Development implements the feature from the same Gherkin feature file
  4. You make the automated test pass
  5. Repeat
Behavior Driven Development and Testing

click to zoom

If you haven’t already, request an evaluation of Squish 6.0beta, and begin automating features sooner with the introduction of BDD automation.


Squish tip of the week: Using variable values in the Squish Script Console

Segmenting from a past blog post, Scripting with the help of the Squish Script Console, an enhancement to the Squish Script Console in 6.0 makes current variables and their values available from the console.

Now manually scripting or troubleshooting your scripts are that much easier!

The example below illustrates using the record variable value in a statement within the Squish Script Console to validate expected output and syntax.

Click to zoom