Blog

  • Support for testing Chromium-based desktop applications with Squish for Web

    By on April 25, 2017

    Motivation Adding HTML/Web support to a desktop application, or even providing a desktop application that’s almost completely built with Web technologies, is quite a popular way of providing modern and fast-evolving user interfaces and applications. There are some projects that embed an almost complete web browser into the application, while others focus on providing a ready-made shell for showing a web application to users on desktop platforms. Many of these projects use the Chromium browser component that Google Chrome is based on, for example Chromium Embedded Framework, Electron or nw.js to name just a few. One thing these Chromium-based frameworks have in common is that they remove or disable some of the features that a full-blown browser has, for example, they usually do not provide support for installing extensions into the browser. That has been a problem for Squish for Web so far since it heavily relies on information...

    Read more
  • How to design good BDD steps

    By on April 18, 2017

    Some time ago I started to work on a new product and we decided to do the tests with BDD. I learned some lessons from the experience of doing real world BDD tests. Designing good BDD steps is especially an ongoing process. In this blog article I want to share some insight I gained. This article is for readers already familiar with the basics of BDD and Gherkin. Short steps for easy scenario variations If your steps do just a single simple action, it is easy to combine them to new scenarios: you can achieve variations of scenarios without writing new step implementations. Take for example a web site where you can add comments to articles, reply to comments, and modify comments and replies. One scenario could be: Feature: ... Scenario: Reply to edited comment ... When I log in as Arthur Dent And I add a comment to the first article with...

    Read more
  • Squish adds support for web testing with Microsoft Edge

    By on April 11, 2017

    So far Squish for Web, which supports a wide range of web browsers for automated Web testing, didn’t support Microsoft Edge. The Edge browser was introduced with the release of Windows 10 and is replacing Internet Explorer as the default browser on Windows. With the upcoming release of Squish 6.3 we will finally add official support for the new browser from Microsoft. The Edge browser will be the first browser that Squish automates using the Webdriver API. The same API will also be used to add support for the Chromium Embedded Framework. We leverage this technology in the future to further improve our ability to do web testing on mobile devices. Webdriver Squish uses a wide range of techniques to be able to automate the different supported browsers. While Squish uses a COM-Interface to automate Internet Explorer, for both Chrome and Firefox custom browser plugins were developed. What all the different...

    Read more
  • BDD - Behavior-Driven Development & Testing

    How to execute only desired BDD scenarios

    By on April 4, 2017

    When doing BDD testing sometimes there is a need to execute only certain scenarios instead of all the scenarios of the feature file. Tags are a great way to organize/group your Scenarios. One can use squishrunner’s  – -tags option to execute just those BDD secnarios which match a given tag filter. Setting a tag filter for BDD scenarios: In the example below @foo and @bar tags are used to tag scenarios. Feature: Filling of addressbook As a user I want to fill the addressbook with entries @foo Scenario: Initial state of created address book Given addressbook application is running When I create a new addressbook Then addressbook should have zero entries @bar Scenario: State after adding one entry Given addressbook application is running When I create a new addressbook And I add a new person 'John','Doe','john@m.com','500600700' to address book Then '1' entries should be present @foo @bar Scenario: State...

    Read more
  • Debugging Coco with the verbose build mode

    By on March 28, 2017

    When an application is instrumented with Squish Coco and problems arise, it is often helpful to run the compilation in the verbose build mode. This is especially useful when some of the program files are excluded from the instrumentation. With the verbose build enabled, one can see which files are read, which of them are included in the instrumentation, and which command line option was responsible for the inclusion. This also helps to find the reason why a function was not included in the code coverage.

    Read more
  • Verifying Custom Properties of a QObject in Squish

    By on March 23, 2017

    If you’re testing a Qt-based application with Squish, you probably know the problem: one of your classes has custom properties you would really like to verify, but you cannot seem to get hold of it from a test script. First the bad news: making it available requires changing your application. The good news: the required changes are really simple! Consider this example class. It has a collection of members and properties which can be used just fine from C++ code: class FrogView { Q_OBJECT public: enum FoodType { Fly, Grasshopper }; FrogView(QWidget *parent = 0); QString name(); void setName(QString name); QList<QString> preferredFood(); signals: void quack(); public slots: void feed(FoodType type); private: QString m_name; }; Note: You probably noticed at once that we should really use the FoodType enum as return type for preferredFood() instead of returning plain strings. That is true of course, but let’s keep it this way...

    Read more
  • Code Coverage Case Study: Learn How InnovMetric Software Benefits from Squish Coco

    By on March 21, 2017

    InnovMetric Software Inc., the leading provider of universal 3D metrology software solutions, started to use froglogic’s Code Coverage Tool Squish Coco in 2015. The main objective was to understand how much of their applications’ code is properly tested by their 15,000+ tests. After some time InnovMetric’s engineers concluded: “Coco seemed like a regular code coverage tool at first, but after we started using it, we found some very advanced features.”. Read the whole story at https://www.froglogic.com/squish/success-stories/coco-case-study-innovmetric/.

    Read more
  • Hybrid Qt on Android App Testing

    By on March 14, 2017

    Squish-6.1 for Android now has support for the UIAutomator framework for Android 4.3 or newer. Qt applications running on Android have C++ and Java code bundled together and running side-by-side. Squish can access objects from each language, but from a single test case, we must distinguish between these two parts of an application somehow. We achieve this with the Application Context. Testing an application running on Android with Squish requires usage of the built-in hook to access Qt objects from Squish. Squish can access such a running app from a test script, using the attachToApplication function.

    Read more
  • Automatically create and update JIRA tickets based on Squish test results

    By on March 7, 2017

    Squish can be used for creating and updating JIRA tickets in response to fails and errors of nightly scheduled test runs automatically. It is possible to give an automated build test its own corresponding JIRA ticket.  These tickets can be assigned automatically to specific people, based on latest errors or changes which happened. In addition, overall statistics for the entire test suite’s life-cycle is available.

    Read more
  • Squish and Functional Mockup Interfaces (FMI)

    By on February 28, 2017

    When testing an application that interfaces with external devices, one often doesn’t want to use an actual device. A typical testing setup in such cases would encompass a simulation tool that mocks the device(s) in a predictable and controllable way. Testing using simulated devices have a range of benefits: No need for an actual device, No risk of damaging the device with erroneous commands, Simulation can mock rare conditions: e.g. device malfunction, Simulation can provide the test environment with it’s current state, Simulation can be controlled by the test environment. There is a large number of tools available on the market that allow simulation of various devices, especially used in embedded software development. Many of those tools are capable of communicating with other tools using Functional Mockup Interfaces – FMI. FMI Interface Functional Mock-up Interface (FMI) is a standard describing binary interface between simulation applications. It allows sharing the simulation data and...

    Read more
  • We met Squish users in Poland for “UI Behavior Driven Testing” workshop

    By on February 27, 2017

    On Wednesday, 22 February 2017, our Squish experts Tomasz Pawlowski and Jakub Topolski conducted a “Squish in Action: UI Behavior Driven Testing” one-day workshop. We met with 16 participants in the beautiful city of Gdansk (Poland). Shortly after 9am we started with a decent theoretical introduction to Behavior Driven Development. After that, we split up the participants into 4 groups with a task to create BDD Scenarios in the Gherkin language. The participants then were introduce to the Squish GUI Tester to start automating those Scenarios. In the meantime we had Pizza giving us some time to relax and do some networking. After the break, we presented how to implement each Scenario giving our participants some time to practice the same with their own Squish installation. While doing that we demonstrated how to interact with objects, widgets, properties & the API. With Squish’s true object-level access and Behavior Driven Testing...

    Read more
  • Define your own Symbolic Names

    By on February 21, 2017

    Usually when Squish adds an object to the Object Map, Symbolic Name is created as a combination of its properties (e.g. caption and type of the selected object). Thanks to that, most of the time it’s easy to identify objects behind these names. However, there are cases where it is not enough. We would like to show you a different approach of defining your own Symbolic Names, even before you start to write your first functional test case. On the image below you can see an “Address Book – Add” dialog from our example application – Addressbook. Here is a list of Symbolic Names of objects located in this dialog. :Address Book - Add.Cancel_JButton :Address Book - Add.Email:_JLabel :Address Book - Add.Email:_JTextField :Address Book - Add.Forename:_JLabel :Address Book - Add.Forename:_JTextField :Address Book - Add.OK_JButton :Address Book - Add.Phone:_JLabel :Address Book - Add.Phone:_JTextField :Address Book - Add.Surname:_JLabel :Address Book -...

    Read more
  • 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 is to figure out what went wrong, and that’s where a good test report shines.

    Read more
  • The Squish Jenkins plugin now supports Pipelines

    By on February 6, 2017

    As we received a lot of questions about using the Squish Jenkins Plugin in Pipeline jobs, we now introduced a solution for that. Starting from the version 7.0 of the Squish Jenkins plugin support for Pipelines is available. If you are interested in short tutorial please read the Knowledge Base article. More information can be found in the Squish Plugin documentation.

    Read more
  • Overriding Squish functions

    By on February 1, 2017

    Motivation There may be cases where one wants to change the behavior of the functions provided by Squish. For example, even though the default timeout of waitForObject() is 20 seconds (which usually is enough for a GUI control to be “visible and enabled”), in some rare cases one may find that this is still not enough time. One would usually handle such cases individually by adding a second parameter to the respective waitForObject() call, which stands for the desired timeout in milliseconds: // Let's wait for up to 40 seconds for ":x": waitForObject(":x", 40000); But, what if there are many more places where such a change would needed? Then we would have to go through our script, adding the timeout parameter to all the other desired waitForObject() calls, which can be a very tedious and error prone task. Also, we may not even know in advance where these longer...

    Read more
  • Breakpoint marker with Backslash

    Help! Squish Does Not Stop At Any Breakpoint Anymore

    By on January 25, 2017

    In the more recent past, we had a few incidents where customers and even colleagues found out how to disable the breakpoints in their test scripts in the Squish IDE. Unfortunately, they did not really notice how they were doing this and hence needed a little help to re-enable the breakpoints. So we will now have a look at how it looks like when this feature is active, how the breakpoints can be enabled again and what possible uses this feature has. How do I know that my breakpoints are all disabled? The sidebar of the editor shows the breakpoint markers with a blue backslash on top, similar to this screenshot: This backslash indicates that a feature of the IDE (or rather of the underlying Eclipse framework) has been used to disable all breakpoints.

    Read more
  • Code completion

    Upcoming feature “script-based object map”

    By on January 18, 2017

    Upcoming feature: Script-Based Object Map In July 2016 two blog articles presented an alternative script-based Object Map approach for advanced management of object names. The idea is to use script language variables instead of string-based Symbolic Names for object look-up and interaction functions. As shown in the examples below, language specific dictionaries with wildcard and regular expression support are used to define the properties of object names and since the Object Map is written in the same language as the tests, Squish IDE features like code completion, jump to definition and refactoring make usage of object names quite simple. In one of the next Squish releases the script-based Object Map will be supported for all five script languages, including these main features: Recording Playback Script framework for “home brewn” Object Maps How will it look like? Here are small examples for Ruby and JavaScript: Ruby objectmap.rb Address_Book_MainWindow = ObjectName.new({:type...

    Read more
  • Execute tagged scenarios in Maven

    By on January 16, 2017

    Recently released Squish GUI Tester 6.2 allows for Test Case tagging. It was already possible to tag Scenarios in BDD Feature as well. We have just released Squish Maven plug-in version 4.3 which allows to execute only tagged Test Cases or Scenarios. More information: Knowledge Base Article Maven plug-in documentation

    Read more
  • Squish Tip of the Week: Verification of Text Colors

    By on January 4, 2017

    A common thing tests like to verify is whether text has a certain color. If you wish to avoid screenshot comparisons, then the way to do this differs depending on the toolkit and the API you are using to present text to the user. This article will explain some of the different ways text can be presented, and how to verify their color in a test case.

    Read more
  • Merry Christmas 2016

    Merry Christmas 2016

    By on December 21, 2016

    A very successful year at froglogic comes slowly to an end. This year has been successful in may aspects for us. On the business side, we have increased our revenue by 14% compared to 2015 by winning several new customers as well as appreciating continued business from our existing customer base. Since we care a lot about our users being successful with Squish and Squish Coco, this year we have re-invested parts of our profit into increasing our technical support team. This also shows in the support & updates subscription renewal rate: 89% of our customers renewed their support & updated subscription this year which is the best we have ever seen. A big thanks to you, our loyal customers! So we would like to take the opportunity to thank all our customers and partners for the trust and confidence in our work and look forward to the successful continuation of...

    Read more
Load More