Tip of the Week

  • Identifying Poor Object Names – And How To Improve Them

    By on novembre 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...

    En savoir plus
    froglogic
  • Measure code coverage on ARM Cortex-M microcontrollers

    By on novembre 20, 2018

    ARM Cortex-M microcontrollers are becoming more and more popular. This article will show you how to use Squish Coco to get code coverage from one of such microcontrollers.

    En savoir plus
    froglogic
  • Automating Qt applications packaged as AppImages

    By on novembre 6, 2018

    Squish for Qt allows automated GUI testing of Qt applications. Typically automating Qt applications with Squish works out of the box. If it doesn’t, then this may be because the application has been packaged in a special way, for example as an « AppImage » which overwrites some environment variables (LD_PRELOAD...

    En savoir plus
    froglogic
  • View Squish Test results of merge requests in GitLab

    By on octobre 16, 2018

    Introduction It’s very important to make automated GUI tests a part of a Continuous Integration (CI) process. Squish offers add-ons for many popular CI tools like Jenkins, Bamboo and TeamCity. The full list is here. If your tool is not on the list, it can be still integrated as...

    En savoir plus
    froglogic
  • Code Coverage with QTest

    By on octobre 9, 2018

    Today’s tip will show how to measure code coverage for unit tests written using the Qt Test framework (or short QTest). The example A simple example for code that uses Qt which is tested via the Qt Test framework can look like the following. To keep it short the...

    En savoir plus
    froglogic
  • Monitoring long-running tests by intermediary logging of results

    By on octobre 2, 2018

    Motivation The set of tests being run on an application tends to grow as more features are added, or more bugs are fixed. This comes at the cost of execution times: for example, a test suite that took 30 min could now take 2 hours. Since normal logging info/test results...

    En savoir plus
    froglogic
  • Retrieve code coverage data via a remote debugger connection

    By on septembre 25, 2018

    Introduction By default, the code coverage tool Squish Coco creates a file with the extension .csexe upon the application exit with the code coverage information of the current execution. When working on an embedded device, this is not convenient because: Some embedded OSes do not have a file system...

    En savoir plus
    froglogic
  • Find unused functions in C/C++ code with coverage analysis

    By on septembre 18, 2018

    Unused functions impact maintenance Unused functions in a software project can cause code bloat, but they also create more work for the developers of tests, especially in the situation where code coverage (the quality) of tests is being measured. If a function is not used, then removing it from...

    En savoir plus
    froglogic
  • Using Squish to automate Qt Installer Framework UI Tests

    By on septembre 11, 2018

    The Qt Installer Framework got recently support for Squish. In this article you can see how to add Squish support to your installers which are based on this framework.

    En savoir plus
    froglogic
  • Lesser known tips on BDD testing using Squish

    By on septembre 4, 2018

    Behavior-Driven Development (BDD) is an extension of the Test-Driven Development approach which puts the definition of acceptance criteria at the beginning of the development process as opposed to writing tests after the software has been developed. With possible cycles of code changes done after testing. Behavior Driven Tests are...

    En savoir plus
    froglogic