-
Difference between “Object not found” and “Object not ready” errors
Read moreUnsuccessful object 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...
-
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: Automation Setup on Windows
Read moreThere are situations in which test scripts will hang and time out on Windows while executing. Most of this cases involve the lack of drawing/painting the application on the “screen”. The underlying problem is that if the GUI of the application cannot be rendered, its objects do not have...
-
Squish tip of the week: Error debugging with StackTrace
Read moreA StackTrace is a very helpful debugging tool. It shows you the call stack (meaning, the stack of functions that were called up to that point) at the time an uncaught exception was thrown or the time the stacktrace was generated manually. This is very useful because it doesn’t...
