Jest --coverage : help #126

seeliang · 2016-04-01T22:44:41Z

Hi everyone,

is anyway i can setup this with Jest?

many thanks

jseminck · 2016-08-28T08:49:39Z

Just add: && cat ./coverage/lcov.info | ./node_modules/coveralls/bin/coveralls.js

    "test": "node --harmony_proxies node_modules/.bin/jest --coverage && cat ./coverage/lcov.info | ./node_modules/coveralls/bin/coveralls.js",

tizmagik · 2016-09-17T22:49:49Z

Thanks @jseminck would be good to add this to the README, I think?

ndelvalle · 2016-11-04T14:53:28Z

I followed @jseminck approach, but now Im getting the following error:

[error] "2016-11-04T14:51:39.503Z"  'error from lcovParse: ' 'Failed to parse string'
[error] "2016-11-04T14:51:39.505Z"  'input: ' ''
[error] "2016-11-04T14:51:39.506Z"  'error from convertLcovToCoveralls'

Any ideas? Thanks in advanced.

cdaringe · 2016-11-16T21:16:11Z

@ndelvalle, most likely, your coverage/lcov.info is empty

ndelvalle · 2016-11-17T09:28:54Z

yep @cdaringe that was the problem 👍

joseluisq · 2016-12-06T02:03:44Z

👍

bcoe · 2016-12-11T01:59:55Z

@jseminck @seeliang worth noting that Jest's coverage implementation outputs a .JSON report that is compatible with nyc and Istanbul in the coverage/ folder. So this would totally work:

nyc report --temp-directory=coverage --reporter=text-lcov | coveralls

seeliang · 2016-12-11T22:27:39Z

Thanks, guys.
I will give a go later :)

jest works with globals so they have to be added to the Eslint configuration. I decided to move tests next to the files they test (jest picks up files that are name *.test.js) to make them easier to locate. They need to be ignored by babel to not show up in the lib folder (that is published to npm). jest comes with a coverage tool and a watch mode so nyc and npm-watch are no longer needed. nickmerwin/node-coveralls#126 (comment)

jest works with globals so they have to be added to the Eslint configuration. I decided to move tests next to the files they test (jest picks up files that are name *.test.js) to make them easier to locate. They need to be ignored when the code is published to npm (instead of the test folder). jest comes with a coverage tool and a watch mode so nyc and npm-watch are no longer needed. nickmerwin/node-coveralls#126 (comment)

jest works with globals so they have to be added to the Eslint configuration. I decided to move tests next to the files they test (jest picks up files that are name *.test.js) to make them easier to locate. The .test.js files need to be ignored when the application is build (they are not needed to run and are shown as extra testcases otherwise). https://github.com/skovhus/jest-codemods/blob/master/package.json (scripts section) jest comes with a coverage tool and a watch mode so nyc and npm-watch are no longer needed. nickmerwin/node-coveralls#126 (comment) The jest configuration ensures that all src files are checked when the coverage report is created (even when they are never required) and makes sure that the compiled code is ignored.

jest works with globals so they have to be added to the Eslint configuration. I decided to move tests next to the files they test (jest picks up files that are name *.test.js) to make them easier to locate. The .test.js files need to be ignored when the application is build (they are not needed to run and are shown as extra testcases otherwise). https://github.com/skovhus/jest-codemods/blob/master/package.json (scripts section) jest comes with a coverage tool and a watch mode so nyc and npm-watch are no longer needed. nickmerwin/node-coveralls#126 (comment) The jest configuration ensures that all src files are checked when the coverage report is created (even when they are never required) and makes sure that the compiled code is ignored. babel-jest is needed to transform the code (including tests) before it is executed. It just needs to be installed (will be used automatically). ES6 modules do not work without it.

…coveralls#126

For coveralls Ref: nickmerwin/node-coveralls#126 (comment)

iddan · 2017-07-30T08:56:46Z

Can this be added to the README?

nickserv · 2017-09-07T19:49:20Z

👍 For adding to readme.

Is there any advantage to any specific coverage format? Which file in coverage should we pipe into coveralls if we add it to the readme?

  -rw-r--r--   1 nick  staff  10945 Sep  7 15:15 clover.xml
  -rw-r--r--   1 nick  staff  28542 Sep  7 15:15 coverage-final.json
  -rw-r--r--   1 nick  staff  23445 Sep  6 21:46 coverage.json
  -rw-r--r--   1 nick  staff  25730 Sep  6 03:59 coverage.raw.json
  drwxr-xr-x   9 nick  staff    306 Sep  7 13:36 lcov-report
  -rw-r--r--   1 nick  staff   4024 Sep  7 15:15 lcov.info

arkgast · 2017-09-26T04:15:20Z

Why not use a script like this?

jest --coverage && cat ./coverage/lcov.info | coveralls

nickserv · 2017-09-26T16:27:47Z

Personally I like to set "jest": { "collectCoverage": true } in package.json to enable coverage reporting everywhere, add coveralls as a devDependency, and have CI run coveralls < coverage/lcov.info.

arkgast · 2017-09-26T18:05:28Z

😮 now I got it, so most people don't have coveralls as a devDependency that's way ./node_modules/coveralls/bin/coveralls.js appears in their configurations.

I was asking about that part specially.

By the way I think this is the best approach to maintain configurations clearer. As a side effect you had clarify my doubt 😆, thanks man

nickserv · 2017-09-26T18:58:57Z

I don't think that's the case. Assuming that the other technique is to npm install coveralls in CI after a build, it would still install the package to node_modules with a binary in that location. Whether or not you install as a saved devDependency, it will only be executable directly via coveralls if you have it in your $PATH (some CI services like Travis do this automatically) or if you're calling it in an npm script (which does something similar).

dennisja · 2018-02-09T23:45:26Z

@nickmccurdy Your solution isnot supported by create-react-app
It gives the warning below:
Out of the box, Create React App only supports overriding these Jest options:
• collectCoverageFrom
• coverageReporters
• coverageThreshold
• snapshotSerializers.
These options in your package.json Jest configuration are not currently supported by Create React App:
• collectCoverage

nickserv · 2018-02-10T01:25:42Z

Yes, but you can still use jest --coverage in your build script even though the config option isn't supported.

dennisja · 2018-02-10T08:51:15Z

Yeah,
I solved it by run yarn test --coverage which later runs jest --coverage

See nickmerwin/node-coveralls#126 (comment)

ummahusla · 2018-02-22T09:27:13Z

This is how I got it to work

node_modules/.bin/jest --coverage && cat ./coverage/lcov.info | ./node_modules/coveralls/bin/coveralls.js

jeff1evesque · 2018-05-31T16:50:58Z

@jseminck, @tizmagik: sorry to bother in this thread. I'm using jest + enzyme, and hoping to pipe the coverage results to coveralls. So, I implemented test:coveralls, a script from my package.json:

  "scripts": {
    "build:browserify": "browserify -t [ babelify --presets env,stage-2,react ] content.jsx > ../../interface/static/js/content.js",
    "prebuild:dos2unix": "find . -type f -print0 | xargs -0 dos2unix",
    "watch:jsx": "onchange 'src/jsx/**/*.jsx' 'src/jsx/**/*.js' -- npm run build:browserify",
    "test": "NODE_ENV=test jest --config jest.config.js",
    "test:coveralls": "npm run test --coverage --coverageReporters=lcov.info | ./node_modules/coveralls/bin/coveralls.js"
  },

I've verified both coveralls.js, and lcov.info are nonempty. However, my travis build, seems to error:

[error] "2018-05-31T16:37:12.946Z"  'error from convertLcovToCoveralls'
/home/travis/build/jeff1evesque/machine-learning/src/jsx/node_modules/coveralls/bin/coveralls.js:18
        throw err;
        ^
Failed to parse string
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] test:coveralls: `npm run test --coverage --coverageReporters=lcov.info | ./node_modules/coveralls/bin/coveralls.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] test:coveralls script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/travis/.npm/_logs/2018-05-31T16_37_12_965Z-debug.log
The command "npm run test:coveralls" exited with 1.

jeff1evesque · 2018-05-31T19:06:09Z

@jseminck, @tizmagik: nevermind, I think I've fixed it. The corresponding travis build, seems to have run the following without erroring:

cat lcov.info | ./node_modules/coveralls/bin/coveralls.js

I guess I'll merge my corresponding pull request, and see if my webhook updates coveralls.

jeff1evesque · 2018-05-31T19:16:34Z

Ah, didn't have to wait for PR to be merged. Seems like the configurations worked. Thank you everyone, pretty much recycled different aspects from various comments in this issue.

petermikitsh · 2018-07-21T09:41:49Z

@nickmccurdy's solution worked for me. Thanks Nick!

ambroiseRabier · 2019-07-14T09:24:28Z

Based on @jeff1evesque and @nickmccurdy answer:

package.json

"scripts": {
  "ci-process-cover": "cat coverage/lcov.info | coveralls"
}

jest.config.js

module.exports = {
  "collectCoverage": true
  // ...
}

.travis.yml

script:
  - npm run test
after_script:
  - npm run ci-process-cover

Or have tests run twice:

package.json

`cover`: `jest --coverage --coverageReporters=text-lcov | coveralls`

.travis.yml

script:
  - npm run test
after_script:
  - npm run cover

If you replace npm run test by npm run cover, coverage will work, but your CI will not fail if one test fail.

zdrawku · 2021-01-07T16:13:49Z

I've faced a similar problem, hope this post might help you a little bit.

adefemi171 · 2021-01-11T05:31:11Z

Hi all am facing

[error] "2021-01-11T05:26:15.227Z"  'error from lcovParse: ' 'Failed to parse string'
[error] "2021-01-11T05:26:15.230Z"  'input: ' ''
[error] "2021-01-11T05:26:15.230Z"  'error from convertLcovToCoveralls'

when running it locally and in my Github action. How do I generate .lcov so the file won't be empty? @nickmccurdy @jseminck @tizmagik

zdrawku · 2021-01-11T07:43:48Z

@adefemi171 if you are using Angular --code-coverage will generate a coverage report for you.

adefemi171 · 2021-01-11T18:03:53Z

Am using Node and Jest and I ran jest --coverage which created a coverage folder but with an empty lcov.info @zdrawku

Yegorich555 · 2021-11-30T05:40:22Z

Why not use a script like this?
jest --coverage && cat ./coverage/lcov.info | coveralls

Because it doesn't work on Windows.

Do we have any cross-platform solution ?

I figured only following:

jest --coverage && coveralls < coverage\\lcov.info

Ordinary pipe jest --coverage --coverageReporters=text-lcov | coveralls somehow doesn't work with NodeJS 14.15.*

oatycreates added a commit to oatycreates/solitaire-react that referenced this issue Jan 1, 2017

Set up coveralls for React code. With assistance of: nickmerwin/node-…

e89938b

…coveralls#126

coryhouse mentioned this issue Feb 7, 2017

Jest migration coryhouse/react-slingshot#363

Merged

marcusjwhelan mentioned this issue May 2, 2017

confused about purpose of NYC vs Istanbul istanbuljs/nyc#524

Closed

andywer mentioned this issue Jun 1, 2017

PR: Setup coveralls coverage badge amilajack/babel-plugin-fail-explicit#23

Closed

amilajack mentioned this issue Jun 1, 2017

Migrate to coverage based builds instead of pass/fail using coveralls amilajack/falcon-core-old#12

Closed

dijonkitchen added a commit to dijonkitchen/reader that referenced this issue Jun 4, 2017

Modify test script to include test coverage

489610a

For coveralls Ref: nickmerwin/node-coveralls#126 (comment)

sdellis mentioned this issue Dec 1, 2017

Merge Jest coverage with Coveralls test coverage pulibrary/figgy#616

Closed

filipposarzana mentioned this issue Dec 21, 2017

Introduce coveralls on CI homeruntech/react-rating#13

Closed

Glavin001 added a commit to Unibeautify/unibeautify that referenced this issue Feb 13, 2018

Fix Travis CI sending to Coveralls

e14f813

See nickmerwin/node-coveralls#126 (comment)

blindbox mentioned this issue May 5, 2018

implement coverage reports antonve/srs-app-archived#15

Merged

This was referenced May 31, 2018

error from convertLcovToCoveralls #193

Closed

Combine python-coveralls with jest 'collectCoverage' lemurheavy/coveralls-public#1123

Closed

This was referenced Oct 3, 2018

CI hooks coveralls to jest coverage LD4P/sinopia_profile_editor#46

Merged

[WIP] CI hooks coveralls to jest coverage LD4P/sinopia_editor#36

Merged

mlms13 mentioned this issue Jul 12, 2019

Jest instructions cause CI to pass on failed tests #230

Closed

acstll mentioned this issue Oct 17, 2019

Setup coveralls acstll/regierung#2

Open

tay1orjones mentioned this issue Feb 17, 2020

fix(ci): reconfigure coveralls to not swallow error exit codes carbon-design-system/carbon-addons-iot-react#920

Merged

jonaslagoni mentioned this issue Mar 2, 2021

chore: add test coverage badges asyncapi/modelina#120

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Jest --coverage : help #126

Jest --coverage : help #126

seeliang commented Apr 1, 2016

jseminck commented Aug 28, 2016

tizmagik commented Sep 17, 2016

ndelvalle commented Nov 4, 2016 •

edited

Loading

cdaringe commented Nov 16, 2016

ndelvalle commented Nov 17, 2016

joseluisq commented Dec 6, 2016

bcoe commented Dec 11, 2016

seeliang commented Dec 11, 2016

iddan commented Jul 30, 2017

nickserv commented Sep 7, 2017 •

edited

Loading

arkgast commented Sep 26, 2017

nickserv commented Sep 26, 2017

arkgast commented Sep 26, 2017

nickserv commented Sep 26, 2017

dennisja commented Feb 9, 2018

nickserv commented Feb 10, 2018

dennisja commented Feb 10, 2018

ummahusla commented Feb 22, 2018

jeff1evesque commented May 31, 2018 •

edited

Loading

jeff1evesque commented May 31, 2018

jeff1evesque commented May 31, 2018

petermikitsh commented Jul 21, 2018

ambroiseRabier commented Jul 14, 2019 •

edited

Loading

zdrawku commented Jan 7, 2021

adefemi171 commented Jan 11, 2021

zdrawku commented Jan 11, 2021

adefemi171 commented Jan 11, 2021

Yegorich555 commented Nov 30, 2021 •

edited

Loading

Jest --coverage : help #126

Jest --coverage : help #126

Comments

seeliang commented Apr 1, 2016

jseminck commented Aug 28, 2016

tizmagik commented Sep 17, 2016

ndelvalle commented Nov 4, 2016 • edited Loading

cdaringe commented Nov 16, 2016

ndelvalle commented Nov 17, 2016

joseluisq commented Dec 6, 2016

bcoe commented Dec 11, 2016

seeliang commented Dec 11, 2016

iddan commented Jul 30, 2017

nickserv commented Sep 7, 2017 • edited Loading

arkgast commented Sep 26, 2017

nickserv commented Sep 26, 2017

arkgast commented Sep 26, 2017

nickserv commented Sep 26, 2017

dennisja commented Feb 9, 2018

nickserv commented Feb 10, 2018

dennisja commented Feb 10, 2018

ummahusla commented Feb 22, 2018

jeff1evesque commented May 31, 2018 • edited Loading

jeff1evesque commented May 31, 2018

jeff1evesque commented May 31, 2018

petermikitsh commented Jul 21, 2018

ambroiseRabier commented Jul 14, 2019 • edited Loading

zdrawku commented Jan 7, 2021

adefemi171 commented Jan 11, 2021

zdrawku commented Jan 11, 2021

adefemi171 commented Jan 11, 2021

Yegorich555 commented Nov 30, 2021 • edited Loading

ndelvalle commented Nov 4, 2016 •

edited

Loading

nickserv commented Sep 7, 2017 •

edited

Loading

jeff1evesque commented May 31, 2018 •

edited

Loading

ambroiseRabier commented Jul 14, 2019 •

edited

Loading

Yegorich555 commented Nov 30, 2021 •

edited

Loading