-
How to Choose Which GUI Tests to Automate
Read moreAutomating Graphical User Interface (GUI) tests is a challenging task. In theory, any test can be automated, but it is not worth it to automate every test, often because of limited resources (i.e., time spent on writing the automated test.) So how do you decide which test cases are...
-
Running GUI Tests on Each Commit in GitLab CI/CD
Read moreIn a recent article, we wrote about running Squish tests on merge requests in GitLab. In this article, we present a solution to run Squish tests on each commit. Overview We invoke the squishrunner command to execute tests and generate JUnit and web reports. Additionally, squishrunner is called with...
-
Bulk Verifications of Similar Objects
Read moreSquish offers a number of verification points, or VPs: object property verification, screenshot verification, table verification or visual verification. We can create verification points during the initial recording of a test case or while recording a snippet. When doing so we need to select an object that we want...
-
View Squish Test results of merge requests in GitLab
Read moreIntroduction It’s very important to make automated GUI tests a part of a Continuous Integration (CI) process. Squish offers add-ons for many popular CI tools like Jenkins, Bamboo and TeamCity. The full list is here. If your tool is not on the list, it can be still integrated as...
-
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...
-
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...
-
Approaches to creating BDD Scenarios
Read moreBehavior Driven Development uses conversations around concrete examples of system behavior to get a common understanding of features that are going to be implemented. This is the heart of BDD, as the quality of those examples affects the whole development process. How to organize this conversation in practice? There...
-
We met Squish users in Poland for “UI Behavior Driven Testing” workshop
Read moreOn Wednesday, 22 February 2017, our Squish experts Tomasz Pawlowski and Jakub Topolski conducted a “Squish in Action: UI Behavior Driven Testing” one-day workshop. We met with 16 participants in the beautiful city of Gdansk (Poland). Shortly after 9am we started with a decent theoretical introduction to Behavior Driven...
-
Execute tagged scenarios in Maven
Read moreRecently released Squish GUI Tester 6.2 allows for Test Case tagging. It was already possible to tag Scenarios in BDD Feature as well. We have just released Squish Maven plug-in version 4.3 which allows to execute only tagged Test Cases or Scenarios. More information: Knowledge Base Article Maven plug-in...
-
Squish tip of the week: How to describe your automated tests
Read moreWhile working on automating test cases, it is important to describe them well. After some time, the number of automated test cases can be enormous. Giving your test suites and test cases self-explaining and meaningful names can help in the future when you try to find a particular test...
