-
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...
-
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...
-
Upcoming Squish GUI Tester 6.4 Feature: Fuzzy Image Lookup
Read moreSquish 6.3 introduced the image lookup feature. It allows capturing an image of an AUT control during test case recording. During test replay it allows finding the screen position of the specific image and interaction by clicking or tapping at the found position. It is the only way to...
-
Verify objects that appear only for short durations
Read moreMany applications that carry out a long-running task in the background display a dialog indicating the progress of the task. The dialog may block access to the application too if other actions do not make sense while the task is running. These dialogs usually appear and disappear by themselves,...
-
Squish Tip: Synchronization with waitUntilObjectReady()
Read morewaitUntilObjectReady() is a callback function that by default, does nothing, but it can be defined in your test scripts to do anything you want. The method is called just before waitForObject() returns, and gets as an argument, the object that Squish thinks is now ready to get events. It...
-
Debug Qt application while running Squish GUI tests
Read moreSome issues with Application Under Tests (AUT) appear only when a test is executed with Squish. For some cases, it’s easier run our test scenario with Squish than repeating it manually. To get a detailed information about the state of our AUT during a test execution, you can attach...
-
Squish GUI Testing Case Study: Topcon Agriculture Group replaces manual testing with Squish Automated Tests
Read moreTopcon Agriculture Group makes a line of Console Displays, GPS systems running embedded Linux and software written in Qt. For 5 years, Topcon has been using froglogic Squish to develop and run almost 1000 automated tests against these devices saving their field testers a lot of time: “Within the first year...
-
Define your own Symbolic Names
Read moreUsually 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...
-
Overriding Squish functions
Read moreMotivation 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...
-
Improved Management Of Object Names – Part 2
Read moreIn 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...
