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

JS Coverage

by genbit ALL Missing

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

Details

Installs

  • Total 798
  • Win 259
  • Mac 397
  • Linux 142
Oct 1 Sep 30 Sep 29 Sep 28 Sep 27 Sep 26 Sep 25 Sep 24 Sep 23 Sep 22 Sep 21 Sep 20 Sep 19 Sep 18 Sep 17 Sep 16 Sep 15 Sep 14 Sep 13 Sep 12 Sep 11 Sep 10 Sep 9 Sep 8 Sep 7 Sep 6 Sep 5 Sep 4 Sep 3 Sep 2 Sep 1 Aug 31 Aug 30 Aug 29 Aug 28 Aug 27 Aug 26 Aug 25 Aug 24 Aug 23 Aug 22 Aug 21 Aug 20 Aug 19 Aug 18
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