Remove the top-level expect

[sunesimonsen]

When using the top-level expect instead of the wrapped expect, we will end up serializing errors that we shouldn't. This PR make sure that we will use the wrapped expect instead.

[coveralls]

Pull Request Test Coverage Report for Build 790

• 27 of 27 (100.0%) changed or added relevant lines in 1 file are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.09%) to 91.29%

---

Files with Coverage Reduction	New Missed Lines	%
lib/index.js	1	92.27%

Totals
Change from base Build 784:	-0.09%
Covered Lines:	517
Relevant Lines:	547

---

💛 - Coveralls

[sunesimonsen]

Before:

After:

[papandreou]

Neat! That has been annoying me for a long time.

The same trick also works in unexpected-messy: unexpectedjs/unexpected-messy@2257aa1

Kinda feels like this should be a first class feature in Unexpected. I guess we can take a look at that when we get around to take a look at errorMode in general.

[alexjeffburke]

The change feels like it's using the facilities available in Unexpected more appropriately - particularly like that it contains setting the errorMode in a single place.

[sunesimonsen]

Kinda feels like this should be a first class feature in Unexpected. I guess we can take a look at that when we get around to take a look at errorMode in general.

Yes that is my thinking as well, but I wanted to try it out here first. I think we could have an:

expect.withErrorMode('bubble', () => { ... })