Coverage Reports with Jest

GitLab CI/CD
1

I am trying to get code coverage working on several repos we have on GitLab. We use JUnit to generate unit tests and we can successfully generate the unit test report in the merge request. That coverage percentage does not populate the code coverage badge on the repo page, nor does it populate the Code Coverage Statistics in the Repository Analytics page for the repository.

This is the relevant part of the gitlab yml file:

.npm-test:
  extends: [.npm-image, .npm-cache-pull]
  dependencies: [install]
  coverage: /All files[^|]*\|[^|]*\s+([\d\.]+)/
  script:
    - npm run test-ci
  artifacts:
    when: always
    paths:
      - junit.xml
    reports:
      junit:
        - junit.xml

We are able to generate the junit.xml file successfully with both Jasmine/Karma and Jest for unit tests. For 3 out of 20 repositories we have, the code coverage badge and analytics are populated correctly with just the junit.xml file. For the rest, the badge and analytics are unknown and empty. I have several questions.

  1. Is Cobertura required to populate the code coverage badge and the code coverage statistics in the analysis page?
  2. If Cobertura is required, why do some of the repos correctly post the statistics?
  3. Does running Cypress in another step in the pipeline affect whether the statistics are reported correctly?
  4. Is there a gitlab setting in the individual repos that affects the code coverage generation?

I have scoured the gitlab documentation and have not been able to reconcile these discrepancies.

We are using the enterprise version of gitlab.

Thanks so much in advance!

2

I don’t think any of the first three are needed. As for your fourth question

Are the projects that do not report code coverage using the right code coverage regex in their CI/CD job(s)? They need that in addition to configuring the badge URL in the project’s Settings ≫ General ≫ Badges.

I assume you already read the Test coverage report badges documentation. Instead of using the literals suggested there, I’d use the %{project_path} and %{default_branch} placeholder so you can reuse that URL across projects.

Hope this helps,