Author archive for Frerich Raabe

  • Screenshots in Squish Reports: Simplifying Result Analysis

    By on October 23, 2019

    The Squish GUI Tester excels at verifying an application’s user interface. But comprehensive verifications can come at a cost: the resulting test reports become huge and daunting to analyze. Take advantage of additional screenshots in Squish reports to get a better understanding of what happened.

    Read more
    froglogic
  • Leveraging Python Packages For Better UI Testing

    By on April 23, 2019

    Python is a very popular language, and for good reason. A wealth of production-quality packages for performing all kinds of tasks is freely available on the Internet. But did you know that all this power is readily available in Squish tests, too? This article explains how to extend the...

    Read more
    froglogic
  • Identifying Poor Object Names – And How To Improve Them

    By on November 27, 2018

    A stable method to address GUI controls is crucial for a maintainable test project. But how does Squish go about generating object names? What makes a good object name? How can you identify poor object names? How can you configure Squish to generate (or reuse) better names? We will...

    Read more
    froglogic
  • BDD Test Cases in Squish: Clean Up After Your Scenarios!

    By on June 12, 2018

    Squish allows creating functional tests for user interfaces in a behaviour-driven (BDD) style, enabling the tester to concentrate on what the user does (“enter user name, confirm login dialog”) instead of how it is done (“enter this, click there”). Leveraging the scripting languages supported, a very elegant scheme for…

    Read more
    froglogic
  • Squish Tip: Good use of the waitFor() function

    By on December 12, 2017

    The Squish script API features a useful function called waitFor; what’s less known is the fact that this function not only supports being called with a script statement but also with an arbitrary callable value.

    Read more
    froglogic
  • Finding & Fixing Dependencies Between Test Cases

    By on July 18, 2017

    Works for me! Did you ever hear yourself uttering those words, or maybe you heard them from a colleague? Tests which work on one system may fail on another. This can happen for many reasons: the application under test (AUT) depends on the operating system on which it is...

    Read more
    froglogic
  • More Useful Squish Test Reports

    By on February 15, 2017

    Test reports matter. Especially so when something goes wrong because Squish detected a failing verification during test execution. When a test fails, it’s typically interesting to figure out why a test failed (except if you’re fine with just ignoring the result). The first step to figuring out why something went wrong...

    Read more
    froglogic
  • Open source C++ execution trace framework

    By on September 15, 2016

    At froglogic, we’re big fans of open source software. A large part of our engineering (and management!) staff contributed or contributes to open source projects, and everyone visiting our offices for a job interview certainly gets a big +1 in case she can show off some open source work!...

    Read more
    froglogic
  • Improved Management Of Object Names – Part 2

    By on July 25, 2016

    In a previous blog entry, we introduced an alternative, script-based, approach to maintaining a mapping of symbolic names (variables) to the actual object names (strings). By using script variables instead of free-form strings, the mapping was no longer stored in a separate text file but instead it was brought...

    Read more
    froglogic
  • Improved Management Of Object Names

    By on July 19, 2016

    TL;DR: Using plain script language variables over the standard objects.map file simplifies refactoring and maintenance at the expense of losing the ability to generate (or reuse) the names when recording. NOTE: Throughout this blog article, we will use the JavaScript language for code samples. Everything shown here can be...

    Read more
    froglogic