Skip to content

issues Search Results · repo:karma-runner/karma-coverage language:JavaScript

Filter by

264 results
 (84 ms)

264 results

inkarma-runner/karma-coverage (press backspace or delete to remove)

Hi So recently migrated over to this package, and since we have a mono-repo of a front-end, which includes multiple different path and sometimes a few nested components. When trying to view a coverage ...
  • lancechant
  • Opened 
    on Nov 21, 2024
  • #507

We are experiencing disconnects of the browser almost 100% of the time with karma-coverage. It used to happen on occasion, but now it happens consistently. On a MacBookPro it rarely happens, but we do ...
  • arobinson
  • 1
  • Opened 
    on Dec 5, 2023
  • #496

Vulnerability: https://github.com/advisories/GHSA-c2qf-rxjj-qqgw https://github.com/karma-runner/karma-coverage/blob/55eb8a85f8243af3ae9cf75460a780fc5c71761f/package.json#L29 Upgrade to istanbul-lib-instrument@6.0.0 ...
  • lsrael-BGx
  • Opened 
    on Jul 25, 2023
  • #492

When using repor type= text the number of row characters were limited to 80. Ex: { type: text , subdir: . , file: full-coverage.txt } we are seeing the response as below -------------------|---------|----------|---------|---------|------------------- ...
  • kumar-tadepalli
  • Opened 
    on Jun 7, 2023
  • #491

coverageReporter: { dir: require( path ).join(__dirname, ./coverage/app ), subdir: . , reporters: [ { type: text-summary }, { type: lcov } ], includeAllSources: ...
  • SenorPez
  • 3
  • Opened 
    on May 18, 2023
  • #490

As described here, when the file parameter of a reporter inside the reporters array of karma.config.js is NOT provided, the exit code will always be 0 even if the coverage requirements are not met.
  • FrancescoBorzi
  • 2
  • Opened 
    on Dec 8, 2022
  • #485

Using the NodeJS API, let s say our config is like this: let KarmaConfig = { plugins: [ karma-chai , karma-mocha , karma-sourcemap-loader , karma-webpack , karma-mocha-reporter , karma-chrome-launcher ...
  • neutraali
  • Opened 
    on Aug 10, 2022
  • #480

My Angular lib itself is targeting ES2017. I tried swapping out test tsconfig to anything newer beyond ES5 - and 90% of my test coverage fails when running karma with --code-coverage. Is there no support ...
  • Ketec
  • Opened 
    on Jul 19, 2022
  • #479

Hi, Is it possible that the coverage report to consider focused tests? In our big project, developers may by mistake push code with fdescribe and we have a rule in CI to check the minimum coverage and ...
  • rmeshksar
  • 1
  • Opened 
    on Jul 13, 2022
  • #478

I have this config: It works but coverage is on test files only. So 100% :-)). I need coverage only on .ts files, but I dont know how set preprocessor only to .ts files. module.exports = function (config) ...
  • Merynek
  • 1
  • Opened 
    on Apr 27, 2022
  • #474
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub