-
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...
-
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...
-
Squish tip of the week: Object Not Found Dialog
Read moreWhen does the Object Not Found Dialog appear? The object not found dialog automatically shows up during the execution of tests in the Squish IDE if a “waitForObject” command runs into a specified (or default) timeout. Furthermore, the dialog will show the error message generated for the lookup error...
-
Squish tip of the week: How to modify the WaitForObject timeout
Read moreTroubleshooting a script can be long and exhausting especially if there are objects which can not be found. Fortunately, we can adjust the timeout duration for waitForObject to save us some time. By default the duration of waitForObject is 20000 milliseconds (20 seconds), which looks like this: During the...
-
Squish tip of the week: Screenshot Verification Point
Read moreThe most commonly used verifications in Squish are object property verifications – comparing the object properties values with an expected value. Those verification points can easily be inserted into a test script using the Squish IDE’s point & click interface. This method is sufficient and for most scenarios best...
