Testwell CTC++ · Integrations

In your toolchain, without changing it

Testwell CTC++ is a set of command-line tools. It sits in front of your compiler, in your IDE, your build and your continuous integration, and works with your test and simulation tools. You keep your compilers, your targets and your methods.

0changes to your source files: instrumentation works on a temporary copy
3steps — instrument, test, report — each one a command line
4step-by-step guides in the online help: Visual Studio, IAR, Eclipse, CMake
The principle

Three steps, in the tools you already use

Each step runs from the command line: it fits into an IDE, a makefile or a continuous integration server.

01

Instrument at build time

The ctc command is placed in front of the compiler call: the code is instrumented on a temporary copy, then compiled by your compiler, with its options. Your sources are not modified.

Build
02

Run your tests

Unit, integration or system tests, automated or manual: the instrumented program records coverage during execution, on the host or on the target.

Tests
03

Produce the reports

The HTML report for the team; XML, CSV or JSON exports for your dashboards and your continuous integration.

Reports
Integrations

With your tools, from the IDE to the dashboard

The main integrations of Testwell CTC++. The guides cited are those of Verifysoft's online help.

◆

IDEs

Instrument and view coverage from the development environment.

  • Microsoft Visual Studio, with a graphical add-in guide ↗
  • IAR Embedded Workbench guide ↗
  • Eclipse CDT guide ↗
  • By configuration: Code::Blocks, Microchip MPLAB, Keil MDK-ARM…
◆

Build and continuous integration

The instrument, test, report cycle is automated on the build server.

  • CMake: a switch in CMakeLists.txt, or the ctclaunch tool guide ↗
  • make, makefiles and build scripts
  • Jenkins and other continuous integration servers
◆

Test tools

Coverage is measured during the tests you already run, whatever tool drives them.

  • Razorcat Tessy
  • PikeTec TPT (Time Partition Testing)
  • Schleissheimer ATS (Automation & Testing Suite)
  • Unit testing frameworks
◆

Models, simulation, AUTOSAR

For code generated from models and for virtual ECUs.

  • MATLAB/Simulink
  • dSPACE TargetLink, VEOS and SystemDesk
  • AUTOSAR Builder
  • Synopsys Silver and TestWeaver
◆

Targets and debuggers

On an embedded target, coverage data is sent back through the channel of your choice.

  • Any embedded target, including highly constrained ones
  • Debuggers and trace tools, including Lauterbach
  • Fully customizable data transfer
◆

Quality and analysis

Coverage joins your quality indicators and your reviews.

At Verifysoft: the "Integrations" chapter of the online help 10.4 ↗  ·  integrations in third-party tools ↗

Compilers and targets

Your compiler stays the project's compiler

Testwell CTC++ works with native and cross compilers, C and C++. Each compiler has a configuration, set up once; many configurations are supplied, and a compiler that isn't listed is adapted quickly and at no charge.

At run time: Windows, Linux and macOS on the host, and any embedded target, including highly constrained ones (little RAM or ROM, no file system).

Your tool isn't on the list?

Tell us about your compiler, your target and your tools: we will check with Verifysoft how Testwell CTC++ integrates with them.

Contact us →

Free trial  ·  Testwell CTC++  ·  Certification  ·  Testwell CTC++ or gcov?