Archive for October, 2018

  • Analyse test reports from automated executions in the Squish IDE

    By on October 30, 2018

    Executing Squish tests regularly in an automated fashion (like in a CI system) is key to a successful test effort. These tests will occassionally fail and then a tester needs to analyze what has caused the failure and possibly adapt the expected values for verifications. The Squish IDE provides...

    Read more
    froglogic
  • Using multiple Firefox profiles from Squish for Web

    By on October 23, 2018

    Introduction All web browsers, when running, store data in a ‘profile’ directory, which contains things like bookmarks, cache, cookies, and offline data. When developing automated regression tests with Squish for Web, the data in the profile can change the behavior of the browser, and sometimes even cause some passing...

    Read more
    froglogic
  • froglogic Included in Gartner’s Master Shift-Left Testing and Increase Feedback to Improve Code Quality Report

    By on October 17, 2018

    froglogic, with its code coverage analysis tool Coco, was included in the Gartner September 2018 report “Master Shift-Left Testing and Increase Feedback to Improve Code Quality” as a vendor for code analysis tools with a focus on code maintainability and reliability. Gartner states in this report: “Poorly written and...

    Read more
    froglogic
  • View Squish Test results of merge requests in GitLab

    By on October 16, 2018

    Introduction 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...

    Read more
    froglogic
  • Code Coverage with QTest

    By on October 9, 2018

    Today’s tip will show how to measure code coverage for unit tests written using the Qt Test framework (or short QTest). The example A simple example for code that uses Qt which is tested via the Qt Test framework can look like the following. To keep it short the...

    Read more
    froglogic
  • Monitoring long-running tests by intermediary logging of results

    By on October 2, 2018

    Motivation The set of tests being run on an application tends to grow as more features are added, or more bugs are fixed. This comes at the cost of execution times: for example, a test suite that took 30 min could now take 2 hours. Since normal logging info/test results...

    Read more
    froglogic