Posts tagged with ‘Coco’

  • Squish Coco 4.2 introduces Code Complexity Metrics And Unifies Cross-platform Code Analysis

    By on June 5, 2018

    The froglogic team is proud to announce the Squish Coco 4.2 release. This version introduces new metrics for the Code Complexity Analysis: McCabe and eLOC. Furthermore, it comes with a feature to unify the Code Analysis of Cross-platform applications. Squish Coco is a complete C, C++, C#, Tcl and...

    Read more
    froglogic
  • Coco – How to measure code coverage on embedded systems via CAN Bus

    By on April 24, 2018

    Introduction Squish Coco generates the code execution measurement using streams and by default, the output of these streams is piped to a file on the file system. For embedded devices without a file system, this leads to problems. Squish Coco allows you to redirect the measurements stream via Custom...

    Read more
    froglogic
  • What exactly is cyclomatic complexity?

    By on April 3, 2018

    The cyclomatic complexity is a measurement of the code complexity proposed by McCabe which is often considered as a magic number which allows us to measure the complexity of a program. It is common to say that a function with a cyclomatic complexity higher than 10 is difficult to...

    Read more
    froglogic
  • FreeRTOS and code coverage on embedded systems

    By on February 13, 2018

    Code coverage for embedded systems poses some questions that do not occur with desktop applications. In this post I will show the first steps on how to measure code coverage with Squish Coco on an embedded system. We will use the FreeRTOS Kernel as our example.

    Read more
    froglogic
  • Meet Embedded Software Testing Specialist froglogic at Embedded World

    By on February 7, 2018

    froglogic, the vendor of the automated GUI Testing Tool Squish and Code Coverage Analysis Tool Coco, today announced that it will exhibit at the Embedded World in Nuremberg, Germany end of February. froglogic, an early anticipator for the need for GUI test automation and code coverage tooling for the rapidly transforming embedded markets, expanded...

    Read more
    froglogic
  • Benefiting from combined usage of Squish and Coco

    By on August 29, 2017

    It is sometimes a good idea to use Squish GUI Tester and Coco in the same project. Squish runs the GUI tests, and Coco measures how much code they cover. A problem that often occurs is however that the instrumented AUT does not write any coverage results.

    Read more
    froglogic
  • Debugging Coco with the verbose build mode

    By on March 28, 2017

    When an application is instrumented with Squish Coco and problems arise, it is often helpful to run the compilation in the verbose build mode. This is especially useful when some of the program files are excluded from the instrumentation. With the verbose build enabled, one can see which files are...

    Read more
    froglogic
  • Code Coverage Case Study: Learn How InnovMetric Software Benefits from Squish Coco

    By on March 21, 2017

    InnovMetric Software Inc., the leading provider of universal 3D metrology software solutions, started to use froglogic’s Code Coverage Tool Squish Coco in 2015. The main objective was to understand how much of their applications’ code is properly tested by their 15,000+ tests. After some time InnovMetric’s engineers concluded: “Coco...

    Read more
    froglogic
  • froglogic Delivers Squish Tool Suite for Automated Testing of Embedded Qt GUIs and HMIs

    By on February 1, 2017

    With the rise of modern user interfaces (HMIs) in the embedded industries, new methods to automate the GUI tests of embedded devices are required to develop and ship quality products. froglogic, the innovative firm behind the cross-platform and cross-technology GUI test automation tool Squish and the cross-platform code coverage...

    Read more
    froglogic
  • Bug Location with Squish Coco 3.4

    By on August 17, 2016

    Locating a software failure can be a tenuous and a time intensive operation due to the fact of the explosion of the source code size and their test suite. Also the complexity of some software imposes an organization in which the test team is separated from the development teams....

    Read more
    froglogic