ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

JS Coverage

by genbit ALL

Highlight uncovered lines in the current file based on a previous coverage run.

Details

Installs

  • Total 798
  • Win 259
  • Mac 397
  • Linux 142
Jan 30 Jan 29 Jan 28 Jan 27 Jan 26 Jan 25 Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8 Jan 7 Jan 6 Jan 5 Jan 4 Jan 3 Jan 2 Jan 1 Dec 31 Dec 30 Dec 29 Dec 28 Dec 27 Dec 26 Dec 25 Dec 24 Dec 23 Dec 22 Dec 21 Dec 20 Dec 19 Dec 18 Dec 17
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

SublimeJSCoverage

Highlights uncovered lines in the current file based on a previous coverage run.

Display highlights: Super + Shift + C

Remove highlights: Super + Shift + C + X

Plugin tries to find the latest coverage report in a closest “coverage” directory.

Configuration

We can also configure your where the plugin is going to look for coverage the information. Just go to Preferences > Package Settings > JS Coverage > Settings - User. The configuration should look something like:

{ “coverageDir”: “my_custom_coverage_dir” }

Karma configuration

You may need to install coverage plugin

npm install karma-coverage --save-dev

Karama should be configured to put coverage report to coverage directory, e.g:

reporters: ['coverage'],
...

plugins : [
...
  'karma-coverage'
...
];

...

preprocessors: {
  // source files, that you wanna generate coverage for
  // do not include tests or libraries
  // (these files will be instrumented by Istanbul)
  'public/js/*.js': ['coverage']
},

...

//configure the reporter
coverageReporter: {
  type : 'json',
  dir : 'coverage/'
}

Screenshots

screen shot 2013-10-02 at 8 44 25 am