Did you know that Squish can monitor for various events and dialogs? The events can be handled, allowing scripts to continue where they left off.
For example, in a Windows application you may install an event handler to react to unexpected open message boxes using MessageBoxOpened. The example below demonstrates logging the handled event and closing the message box should the message box appear at any point in the executing script:
Thank you to those who were able to attend the Squish Coco webinar today. Please find a summary of some of the questions (and answers) from the webinar below. Email additional questions to email@example.com (more…)
Programmatically translate objects using Qt’s translation mechanism for internationalization (i18n)
While this scenario applies to Qt-based applications, similar approaches can be taken (excluding the i18n functionality), to test non-Qt applications by using a repository containing translations. Programmatically translate objects within scripts, loading the translations to each language-specific object map.
Large or growing automated GUI test suite? Need to pin-point key tests for smoke testing?
With each sprint, well-suited smoke tests can go a long way to ensure critical application areas are tested.
What if you could generate a report by simply executing your entire test suite, which revealed an optimal execution order for your tests? Which tests covered the most ground, and which added little or duplicate value?
What’s stopping you? You can generate an Optimized Execution Order report using Squish Coco by simply executing your Squish test suite.
Using Squish Coco, create an instrumented executable of your application
Execute each test in your Squish test suite using the instrumented executable
Load each Squish Coco execution report in the CoverageBrowser
Select Tools > Optimized Execution Order
The analysis reveals the optimal execution order as well as the percent of application coverage by test: