Best Of

Hi @george_vlasov,

In this moment [[fallthrough]] (or gcc attr.) is not supported. We do not have this in our plans for the near feature, but it is a valid request, there are several rules which could benefit from fallthrough being correctly handled. Do you have a specific rule which is noisy because of this?

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.