Best Of

Hi @elch ,

If you want to collect coverage metrics you need to switch the build to coverage mode and instrument the EXE.

At any time you can disable the coverage mode and rebuild your EXE to have a clean build without any coverage instrumentation.

Thanks

Hi @elch,

Can you please elaborate command line invocation for generating report.

This is just a single invocation of "cpptestcli" command with a small set of options to generate the coverage reports and send coverage data for DTP for visualization.

Normally the sequence of actions is:

• user modifies the source code
• source is built by Visual Studio builder (msbuild) with coverage instrumentation
• user executes the resultant binary (EXE file). "clog" file is generated
• user invokes "cpptestcli" command line to generate the report, based on "clog" and build data.

Details are in user manual.

Hope that helps!
Thanks,
Mirek

After a cursory reading of https://www.state-machine.com/qtools/qpspy.html and related pages I see two possible challenges with mixing C/C++test with QTools:

• C/C++test needs to instrument code for coverage, while QSpy instruments code for their purposes. Instrumenting instrumented code may yield strange results.
• QSpy needs host-target communication channel. C/C++test would need one as well.
  It seems C/C++test and QTools would step on each other's toes when used together.

Hi @elch,

Yes, "Unit Testing" and "Coverage" license features are required if you want to deploy unit testing practice.

Hi again,

Cobertura is a tool to report code coverage from Java code. Its domain is to report coverage of code which was executed. The format of Cobertura reports is therefore designed to represent code coverage information, like class, method, lines covered (executed at runtime), covered branches, and other code coverage-related information. Cobertura reports do not have notion of test results at all, not even unit tests.
Here is an example of Cobertura report for reference:
https://raw.githubusercontent.com/jenkinsci/cobertura-plugin/master/src/test/resources/hudson/plugins/cobertura/coverage-with-data.xml
Even if Cobertura is tailored to Java, it could possibly represent coverage information (and coverage only) from other languages.

However, static analysis is completely different thing from runtime testing, and its results are of different type.
Static analysis results represent information related to standard compliance issues as a result of C++test "reviewing" source code, errors detected by flow analysis, static analysis violation details, and so on. This is all static data, while Cobertura is meant to represent dynamic results.

Therefore, Cobertura report format is not applicable to static analysis domain. We would not be able to use it to represent results and violations reported by C++test static analysis.

It is not a "standard error" message from the tool. I guess there may be some issue in your local configuration files. Please contact our support team - short streaming session will be the most effective way to solve this problem.

Thanks