An in-range update of wdio-mocha-framework is breaking the build 🚨

[greenkeeper[bot]]

Version 0.5.12 of wdio-mocha-framework was just published.

Branch	Build failing 🚨
Dependency	wdio-mocha-framework
Current Version	0.5.11
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

wdio-mocha-framework is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/DBCDK/tanterne/builds/314502899?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 27 commits.

• 95ec5ac 0.5.12
• 19e4bab Pass through test context
• fc62155 chore(package): update eslint to version 4.13.0
• 6cacad3 Update docs to only reference supported Mocha opts
• 7a0e638 fix(package): update wdio-sync to version 0.7.1
• 7b4d9b1 chore(package): update eslint to version 4.12.0
• 26828da chore(package): update eslint to version 4.11.0
• fd546e8 chore(package): update sinon to version 4.1.0
• 3c5839f chore(package): update eslint to version 4.10.0
• ce01854 chore(package): update eslint-plugin-node to version 5.2.1
• 12ab176 chore(package): update eslint-plugin-import to version 2.8.0
• c5d5bcd chore(package): update eslint-plugin-promise to version 3.6.0
• 1fe385b chore(package): update eslint to version 4.9.0
• 660178c fix(package): update mocha to version 4.0.0
• b17cc1d chore(package): update eslint to version 4.8.0

There are 27 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:

[greenkeeper[bot]]

After pinning to 0.5.11 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[fvsdbc]

Ignored