Author archive for Sébastien Fricker

  • Retrieve code coverage data via a remote debugger connection

    By on September 25, 2018

    Introduction By default, the code coverage tool Squish Coco creates a file with the extension .csexe upon the application exit with the code coverage information of the current execution. When working on an embedded device, this is not convenient because: Some embedded OSes do not have a file system...

    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 Thomas J. 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...

    Read more
    froglogic
  • Coco Tip: Manual testing on a remote system with Coco

    By on October 17, 2017

    In many cases the application to test is not physically located on the tester’s desktop, which requires that the generated application data, such as code coverage information, gets transferred from the target to a host system. This can be realized in different ways: By a manual transfer through a...

    Read more
    froglogic
  • MC/DC Coverage and Short Circuit Explained

    By on May 9, 2017

    Modified Condition/Decision Coverage (MC/DC) is a code coverage metric that is referred to in many safety standards as the highest level of quality. It was first defined to provide an intermediate metric between condition and multiple-condition coverage for integrated circuits. Whereas plain condition coverage was considered too simple, the...

    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
  • Locating Bugs by Comparing Coverage of Two Tests

    By on May 23, 2016

    The typical answer to the question: Which source code line is responsible for a bug? is Use a debugger! However, it’s not always that simple. Here’s why: Without good working knowledge of the code, it can be difficult to set a breakpoint at a pertinent location, enabling you to...

    Read more
    froglogic
  • Are Unit Tests necessary, or do System Tests suffice?

    By on April 25, 2016

    In theory, each new or modified function should be tested. Often, the initial reaction is to have one unit test per code change. It’s not that simple however. Writing unit tests is time consuming, and only makes sense for functions containing non-trivial code or a minimum level of computational...

    Read more
    froglogic
  • Code Coverage with the ARM C/C++ Compiler

    By on February 19, 2014

    Introduction Developing for an embedded environment can often leave you juggling for space. Squish Coco is designed with such constraints in mind, making instrumentation and code coverage possible even on embedded environments. Squish Coco separates the coverage data creation from the analysis, enabling users performing cross-compilation to host the...

    Read more
    froglogic