Artem Govorov

`[email protected]` was reporting a promise rejection reason as the `actual` object, however `chai-as-promised@6` [is now doing `.toString()` on the object](https://github.com/domenic/chai-as-promised/commit/33ce9df10a70625e4ccc2869aab8fd225569c224#diff-488915eae113ff282aeaca84cd2bf625R125) if it's an error. This makes it impossible to get/view/report...

Perhaps `chai` could extend its API to [include an original error into the `AssertionError`](https://github.com/chaijs/chai/blob/cc79e11b511ecbb54e78b1b2308157ee75ee386e/lib/chai/assertion.js#L101) somehow. Because currently the stack from any promise error is simply lost, that is not great...

@lddubeau I see what you mean about mirroring chai semantics. I think there's still an issue of not reporting the caught error back to the test runner though. [This patch...

It's a pretty common need to set up a context, use it for a few tests, then have a nested `describe` to tune a few more things in the context...

@jamestalmage To me the approach you've mentioned in mocha context looks cleaner. > In my mocha example above, any bluebird specific test would need to be declared outside the testWith...

The second one can be expressed a bit shorter: ``` JavaScript [ { name: 'bluebird', bluebird: true }, { name: 'pinkie', pinkie: true }, { name: 'q', q: true }...

> I have seen plenty mocha test suites where it can be really confusing which nested group you are in Discoverability is not just readability. With the example you've provided,...

> how it would be much harder to write a Babel plugin to analyze my proposed structure The issue is that you can't enforce the "best practice" **structure** because you're...

@jamestalmage Mocha doesn't expose a way to combine groups via API, but you are suggesting to. You can perform "hacks" to abuse mocha structure, but in the case of your...

@jamestalmage here is the real life example:  I think I have seen similar plugins in other editors as well.