Google Test emits test execution reports in the JUnit XML format. SonarCloud (i.e. SonarCFamily not sonar-cxx), however, expects test execution reports in CppUnit's XML format which can be gleaned from the implementation. Need to convert somehow (perhaps XSLT) before calling sonar-scanner.
SonarCloud also supports importing coverage reports from gcov or llvm-cov. We'll need to use the latter if we use the macOS-specific workflow in our .travis.yml.
CodeClimate also supports importing coverage reports generated with gcov, but not llvm-cov.
Codacy also supports importing coverage reports from lcov, and this blog explains how to upload coverage data for unsupported languages like C++.
Google Test emits test execution reports in the JUnit XML format. SonarCloud (i.e. SonarCFamily not
sonar-cxx), however, expects test execution reports in CppUnit's XML format which can be gleaned from the implementation. Need to convert somehow (perhaps XSLT) before callingsonar-scanner.SonarCloud also supports importing coverage reports from
gcovorllvm-cov. We'll need to use the latter if we use the macOS-specific workflow in our.travis.yml.CodeClimate also supports importing coverage reports generated with
gcov, but notllvm-cov.Codacy also supports importing coverage reports from
lcov, and this blog explains how to upload coverage data for unsupported languages like C++.