Open greenkeeper[bot] opened 6 years ago
devDependency
testee was updated from 0.7.0
to 0.9.0
.Update to this version instead 🚀
Enable reporterOptions on testee specified reporters like XUnit reporter, fixes issue #180.
Add Contributing docs, fixes issue #181.
The new version differs by 7 commits.
3846b86
0.9.0
97ca7fc
Merge pull request #181 from bitovi/contributing-docs
7a6c2e8
Merge pull request #180 from ivospinheiro/fix-issue-153
3e4c538
Add contributing docs
b1a07e5
Merge branch 'fix-issue-153' of https://github.com/ivospinheiro/testee into fix-issue-153
19122d0
Use reportOptions config as the second argument to report init
49d0d57
Use reportOptions config as the second argument to report init
See the full diff
devDependency
testee was updated from 0.7.0
to 0.9.1
.Update to this version instead 🚀
The new version differs by 5 commits.
f2aee2b
0.9.1
431033a
Merge pull request #188 from bitovi/upgrade-miner
fe6f828
Bump miner version to 1.0.0 (node 12 compatibility)
ae537c8
Merge pull request #183 from bitovi/greenkeeper/launchpad-0.7.1
bb6d7c3
fix(package): update launchpad to version 0.7.1
See the full diff
Version 0.8.0 of testee was just published.
testee
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 Notes
node_modules exposedIn 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, thenode_modules
folder will be ignored automatically to prevent errors.If using a config, the
coverage
option is not changed, so you can still covernode_modules
if you want to for some reason by doing:#170
Commits
The new version differs by 17 commits.
c68a6b6
0.8.0
b1d20c4
updating author information
4e77abc
Merge pull request #170 from bitovi/ignore-node-modules
e3dd52d
not instrumenting node_modules when using the basic
--coverage
optiona2df5f8
Fix Chrome Headless example to show Puppeteer
8d4a0b4
Merge pull request #166 from bitovi/chrome-dome
332c3f6
Use concrete Chrome Headless examples
fa87597
Merge pull request #160 from bitovi/doc-cli-args
13a1f7a
Merge pull request #159 from bitovi/157-document-ff-dbus
a40d49c
Document how to pass command-line args to browsers
21c1db8
Document FireFox's need for D-Bus on Linux
3c36209
Merge pull request #154 from bitovi/greenkeeper/debug-3.0.0
83e54e5
fix(package): update debug to version 3.0.0
874593d
Merge pull request #149 from bitovi/port-safari
893f01b
Merge pull request #151 from bitovi/fail-fast
There 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: