# Coverage not being applied with reportPaths setup

**URL:** <https://community.sonarsource.com/t/coverage-not-being-applied-with-reportpaths-setup/132653>\
**Category:** SonarQube Cloud\
**Tags:** sonarqube, coverage\
**Created:** [December 23, 2024, 6:24pm UTC](https://community.sonarsource.com/t/coverage-not-being-applied-with-reportpaths-setup/132653 "2024-12-23T18:24:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![matheus1lva](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/matheus1lva/32/65377_2.png) [@matheus1lva](https://community.sonarsource.com/u/matheus1lva)\
**Post date:** [December 23, 2024, 6:24pm UTC](https://community.sonarsource.com/t/coverage-not-being-applied-with-reportpaths-setup/132653/1 "2024-12-23T18:24:03Z")

</div>

Im using bitbucket with bitbucket pipeline where the monorepo contains typescript and typescript react files. Before the scanner and security gate pipes, I have test:

```auto
image: node:20
definitions:
  caches:
    pnpm: $BITBUCKET_CLONE_DIR/.pnpm-store
    node: node_modules/**
    nextjs: $BITBUCKET_CLONE_DIR/web/.next/cache

  yaml-anchors:
    - &install-pnpm-script >-
      npm i -g pnpm && pnpm ci:prepare

  clone:
    depth: full # SonarQube Cloud scanner needs the full history to assign issues properly

  services:
    docker:
      memory: 4096
    postgres:
      image: postgres:16
      variables:
        POSTGRES_USER: prisma
        POSTGRES_PASSWORD: prisma
        POSTGRES_DB: tests

  steps:
    - 
    - step: &install-pnpm-deps
        name: install-dependencies
        caches:
          - node
          - pnpm
        script:
          - npm i -g pnpm
          - pnpm ci:prepare
        artifacts:
          - node_modules
          - .pnpm-store
    - step: &lint
        name: Lint
        caches:
          - node
          - pnpm
        script:
          - *install-pnpm-script
          - pnpm ci:lint
    - step: &test-and-sonar
        name: Test and sonar
        caches:
          - node
          - pnpm
        script:
          - *install-pnpm-script
          - pnpm test:core:backend && pnpm test:web
          - pipe: sonarsource/sonarcloud-scan:3.0.0
          - pipe: sonarsource/sonarcloud-quality-gate:0.1.6

pipelines:
  default:
    - step: *install-pnpm-deps
    - parallel:
        - step: *lint
        - step: *test-and-sonar

options:
  max-time: 30
  size: 2x
  docker: true

```

And my sonar-project.properties is:

```auto

sonar.exclusions=**/*.sql
sonar.tests=web,core
sonar.sources=web,core
sonar.test.inclusions= **/*.test.ts,** /*.test.tsx
sonar.javascript.lcov.reportPaths=web/coverage/lcov.info,coverage/lcov.info
sonar.cpd.exclusions= **/*.sql,** /*.test.ts,**/*.test.tsx

```

Upon running test scripts, it generates 2 lcov reports: 1 at the root, and 1 at web/coverage. Upon adding these to reportPaths, it remains not reporting coverage. How to properly do it?

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [December 24, 2024, 8:35am UTC](https://community.sonarsource.com/t/coverage-not-being-applied-with-reportpaths-setup/132653/2 "2024-12-24T08:35:20Z")

</div>

What do the logs say about the import of code coverage?

> [@How to find logs about importing code coverage](https://community.sonarsource.com/t/how-to-find-logs-about-importing-code-coverage/73317):
>
> When coverage data isn’t appearing as expected in SonarQube Server / Community Build or SonarQube Cloud, the first place you should look is the scanner logs. Where do I find the scanner logs?warning This will likely be broken out into its own guide soon The Scanner logs are the output of executing one of the [scanners](https://docs.sonarqube.org/latest/analysis/overview/), either directly or wrapped by one of many integrations, such as the [SonarScanner for Jenkins](https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-jenkins/), [SonarScanner for Azure DevOps](https://docs.sonarqube.org/latest/analysis/scan/sonarscanner-for-azure-devops/), [SonarQube](https://github.com/SonarSource/sonarqube-scan-action)/[SonarCloud](https://github.com/marketplace/actions/sonarcloud-scan) GitHub Actions or [SonarQube](https://bitbucket.org/sonarsource/sonarqube-scan/src/master/) /…