The version 0.8.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of testee.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesnode_modules exposed
In this release, testee will not instrument any files in node_modules for test coverage when using the basic --coverage option.
If you use the --coverage option, the node_modules folder will be ignored automatically to prevent errors.
If using a config, the coverage option is not changed, so you can still cover node_modules if you want to for some reason by doing:
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
greenkeeper[bot]
commented
6 years ago
Version 0.8.0 of testee was just published.
testeeThe version 0.8.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of testee.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
node_modules exposedIn this release, testee will not instrument any files in
node_modulesfor test coverage when using the basic--coverageoption.If you use the
--coverageoption, thenode_modulesfolder will be ignored automatically to prevent errors.If using a config, the
coverageoption is not changed, so you can still covernode_modulesif you want to for some reason by doing:#170
Commits
The new version differs by 17 commits.
c68a6b60.8.0b1d20c4updating author information4e77abcMerge pull request #170 from bitovi/ignore-node-modulese3dd52dnot instrumenting node_modules when using the basic--coverageoptiona2df5f8Fix Chrome Headless example to show Puppeteer8d4a0b4Merge pull request #166 from bitovi/chrome-dome332c3f6Use concrete Chrome Headless examplesfa87597Merge pull request #160 from bitovi/doc-cli-args13a1f7aMerge pull request #159 from bitovi/157-document-ff-dbusa40d49cDocument how to pass command-line args to browsers21c1db8Document FireFox's need for D-Bus on Linux3c36209Merge pull request #154 from bitovi/greenkeeper/debug-3.0.083e54e5fix(package): update debug to version 3.0.0874593dMerge pull request #149 from bitovi/port-safari893f01bMerge pull request #151 from bitovi/fail-fastThere are 17 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: