Code-Coverage | Java Code Coverage Tools | Code Coverage Tools library

It seems the base image we use must have a non-enterprise edition of the Code Coverage tools (which is a requirement). We tested our SonarQube projects commands locally using an enterprise edition of the tools (I have Visual Studio 2022 Enterprise installed on my machine), and the coverage files produced contain the correct data. However, when we used a Visual Studio Professional install, the files are empty just like our Jenkins pipeline.

As stated, this started happening when the base image was updated - in particular it was around November 8th 2021. It seems the base docker image we were using (mcr.microsoft.com/dotnet/framework/sdk:4.8-20220210-windowsservercore-ltsc2019) has the latest 2022 tools, but it must not be an enterprise edition - hence the empty files.

We switched our pipeline over to using dotCover instead to perform the analysis, which works as expected and our SonarQube coverage is back to normal.

Dunno if GitHub action is same like Jenkins. But on Jenkins you need to run test with --browsers=ChromeHeadless. And the error looks like that GitHub is trying to open Chrome.

So try to change your test:ci in package.json

1. SonarQube has replaced supporting typescript keyword with javascript, since last few versions. Use sonar.javascript.lcov.reportPaths for configuring report path instead of sonar.typescript.lcov.reportPaths in your sonar.properties file.
2. As per my knowledge, as of now SonarQube is only supporting coverage integration using lcov.info file. Make sure your karma configuration is generating lcov.info file at configured path.
3. For generating lcov format coverage report, you may follow below steps:

• Using karma-coverage: (Recommended)

  • Make sure (in package.json) you have karma-coverage installed. Generally it is pre-installed with new angular project.
  • Update your karma.conf.js file as below:
    • Add { type: 'lcov', subdir: 'lcov-report' } under karma-coverage reporters.
  • Make sure that you don't have any duplicate configuration.
  • Remove any other coverage reporter and its configuration to avoid conflict.
  • Ideally, your karma.config.js should look like below:

I think it was just a node_modules problem, as your repo worked after download and initialization. I think babel can fail silently if it's dependencies are out of order.

I removed package.lock (because I use yarn to manage things) and then yarn to init the dependecies.

This is likely because with runTestsInSeparateProcesses, PHPUnit starts a new PHP process for every test. And it seems that it does that without Xdebug loaded.

The PHP that is started for each test needs to be the same as the one that you originally started PHPUnit with. Perhaps there is a different PHP binary first in the PATH?

If that is the case, the way to solve it is to make sure the "right" PHP is first in the PATH.

Codecov is not able to process HTML coverage reports. You should ask phpunit to output XML as well by either changing or appending your command to read --coverage-clover coverage.xml

You can view a list of the supported and unsupported coverage formats at https://docs.codecov.com/docs/supported-report-formats

[1] Saved https://web.archive.org/web/20220113142241/https://docs.codecov.com/docs/supported-report-formats

The problem here might be that Cypress does not support extending the configuration file in the way you did, as also stated here: https://www.cypress.io/blog/2020/06/18/extending-the-cypress-config-file/

In my opinion there are two suitable solution approaches:

1. Approach: Use separate configuration files (my recommendation)

As extending an existing configuration file does not work, I would recommend having separate configuration files, e.g. one for local usage and one for the execution in Azure pipelines. You could then simple add two separate commands in your package.json like:

I assume that you upgraded your project to Angular 13. I replaced karma-coverage-istanbul-reporter with karma-coverage and it works fine.

In karma.conf.js, you should replace coverageIstanbulReporter with coverageReporter as follows

I'm noticing that in both cases you are seeing ChromeHeadless have not captured in issue. In the success it took about 1 min 15 sec before it started up. I'm going to make a few assumptions

• you have quite a bit of code being compiled to run
• you're using the agent in the pipeline (which I want to say is not overly powerful)

The good news is that karma has a captureTimeout that defaults to 60,000. I believe if you add this setting to karma.conf and double it you will give time for chrome to handle all of the tests you're making it load.

You may have a second issue where you possibly have a test that is so intense that chrome sometimes stops responding for longer than browserDisconnectTimeout.