-
Improved Syntax Highlighting for the Script-based Object Map
Read moreIntroduction With the release of the Script-based Object Map, we also added some syntax highlighting options to the Squish IDE. As references to the Script-based Object Map will make up a big part of your test scripts, it’s important to be able to see at first glance which scripted...
-
Integrating Java Code Coverage Tools With Squish Tests
Read moreIn test-driven development, a common challenge is to decide which tests to write and how many are necessary. Ideally, one would have as many tests as there are possible deviations in a program’s behavior. This is often very hard to achieve though, so it is necessary to determine how...
-
Using Squish for Windows and Image-Based Object Lookup for Automation via VNC
Read moreIf you are unable to install Squish on the device you want to test, and you are using a GUI toolkit not supported by Squish so that using the Built-In Hook is not an option, you might still be able to test your application using Squish for Windows and...
-
Code Coverage for C# Programs With Visual Studio
Read moreSquish Coco is mostly used for programs written in C++, but it also supports code coverage for C# programs. The preparation of a C# program for code coverage is rather simple, thanks to a Visual Studio add-in that is part of Coco. This post is a short tutorial about...
-
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...
-
Lesser known tips on BDD testing using Squish
Read moreBehavior-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...
-
Automating Java Web Start applications
Read moreThe Squish for Java edition not only supports testing Java Swing/AWT, SWT/Eclipse RCP or JavaFX based applications but also Java Web Start applications. There are two ways to automate an application started via Java Web Start: 1. Start via web browser 2. Start via the tool javaws 1. Start...
-
Difference between “Object not found” and “Object not ready” errors
Read moreObject synchronization functions such as waitForObject or waitForObjectItem may return various error messages. Fully understanding these messages is important to debug a test script. Squish recognizes GUI objects by a subset of their properties and values. In the example below, we would like to click on an object of...
-
SQLite driven testing using Javascript
Read moreData Driven Testing (DDT) is a method to structure tests. It is recommended for a huge set of data which may grow in the future. Code has to be written only once and new data can be fed into the test without touching the code at all which is...
