codeclimate / test-reporter

Code Climate Test Reporter
MIT License
156 stars 76 forks source link

Test Reporter doesn't take into account my updated .yml file #504

Open williamatpaper opened 1 year ago

williamatpaper commented 1 year ago

The first 6 lines of the exclude_pattern section are not getting picked up when I run before-build and after-build. No complex multi test running here.

version: "2"
# docs https://docs.codeclimate.com/docs/advanced-configuration
checks:
  argument-count:
    enabled: true
    config:
      threshold: 4
  complex-logic:
    enabled: true
    config:
      threshold: 4
  file-lines:
    enabled: true
    config:
      threshold: 250
  method-complexity:
    enabled: true
    config:
      threshold: 5
  method-count:
    enabled: true
    config:
      threshold: 20
  method-lines:
    enabled: true
    config:
      threshold: 25
  nested-control-flow:
    enabled: true
    config:
      threshold: 4
  return-statements:
    enabled: true
    config:
      threshold: 4
  similar-code:
    enabled: true
    config:
      threshold: #language-specific defaults. overrides affect all languages.
  identical-code:
    enabled: true
    config:
      threshold: #language-specific defaults. overrides affect all languages.
exclude_patterns:
  - "app/Providers/BroadcastServiceProvider.php" #not technically application code
  - "app/Exceptions/Handler.php"
  - "app/Http/Controllers/Controller.php"
  - "app/Http/Middleware/TrimStrings.php"
  - "app/Infrastructure/JWT/JWTDecoderInterface.php"
  - "app/Services/LaunchDarkly.php" #this test has to be mocked, and so doesn't get counted for code coverage https://launchdarkly.com/blog/automated-testing-in-launchdarkly/
  - "config/"
  - "docker/"
  - "infra/"
  - "node_modules/"
  - "public/"
  - "dist/"
  - "tests/"
  - "src/assets/"
  - "**/*.spec.js"
  - "**/*.md"
  - "**/*.yml"
  - "**/*.yaml"
camillof commented 1 year ago

Hey there, from what I understand, .codeclimate.yml configuration doesn't affect the test-reporter functionality, It depends solely on your test coverage tool report.

Have you experienced changes on the test-reporter based on that configuration?