Michał Kownacki

Seems like before/beforeEach/after/afterEach halt next tests because they are meant to be used as set up and cleanup - not for actual test assertion. What we need is something that...

@nathanboktae As it's in mocha API: > Mocha allows you to use any assertion library you want, if it throws an error, it will work! Allowing only AssertionErrors in both...

I'm not sure, but probably the order should stay the same. I mean, all befores -> all beforeEaches -> test -> all afterEaches -> all afters. `nonBlocking` flag would not...

This is what from my point of view is needed: ``` describe("afterEach", function() { beforeEach(function() { // do some kind of mocking etc.. }); postEach(function() { // verify if mocks...

What about befores?

You can avoid slowing down if you provide a flag indicating if given object may contain cycles longer than one. For example `isEqual(a, b, true)` will mean that a and...

It's a common pattern in many utility libraries. For example http://underscorejs.org/#uniq you can say that your array is sorted which will allow faster algorithm.

For me it looks great. Although it can make a confusion when comparing array to object, because it now shows "E" difference kind and technically what's different is the class,...