-
Making Use of JavaScript Modules
Read moreSquish 6.4 has added support for the JavaScript import and export statements from ECMAScript 2015 (ECMA-262). Here we list some advantages to using JavaScript modules over Squish’s source() utility: Namespaces With source(), the imported script is evaluated in the global namespace. This may result in unwanted name collisions and may...
-
Identifying Poor Object Names – And How To Improve Them
Read moreA 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...
-
Measure code coverage on ARM Cortex-M microcontrollers
Read moreARM 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.
-
Automating Qt applications packaged as AppImages
Read moreSquish 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...
-
View Squish Test results of merge requests in GitLab
Read moreIntroduction 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...
-
Code Coverage with QTest
Read moreToday’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...
-
Monitoring long-running tests by intermediary logging of results
Read moreMotivation 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...
-
Retrieve code coverage data via a remote debugger connection
Read moreIntroduction 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...
-
Find unused functions in C/C++ code with coverage analysis
Read moreUnused 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...
-
Using Squish to automate Qt Installer Framework UI Tests
Read moreThe 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.
