Expand All Collapse All

• How-To
  • Changing the default executable path for Visual Studio 2017 and later
  • Coco instrumentation with QBS
  • Code coverage report for a selection of files
  • Code coverage with ccache
  • Debugging the CoverageScanner API
  • Enabling Code Coverage with the Visual Studio Coco Wizard
  • How to get code coverage of a library from unit tests
  • Increasing Build Log Verbosity for Visual Studio
  • Opening a Visual Studio Console for Compiling
• Installing Squish Coco
  • Installation of Coco under Windows without user interaction
  • Squish Coco Floating License Server Self-Activation
• Integrating Squish Coco with Third Party Tools
  • TestNG
    • Measuring code coverage of web application using Squish Coco & TestNG driven tests
• Known Issues
• Overview
  • Instrumentation of inline functions
• Troubleshooting
  • A template or inline function in a header file has no coverage
  • Coco instrumentation is too slow
  • Compilation fails when warnings are turned into errors
  • Compiler error: Blocks are nested too deeply
  • CoverageBrowser is too slow
  • How to report an issue concerning CoverageScanner
  • Is there a virus scanner on your system?
  • Lambda expressions with Microsoft Visual Studio 2010
  • Linker symbols beginning with "__cs_tb_" are missing
  • Missing .csexe Files when executing an instrumented application
  • MSBuild projects are not instrumented under Jenkins