Feature request: resolvedWith

[mm-gmbd]

There may be a great reason to not include this, but it feels a bit odd (as I'm starting to write some async test cases) to provide a rejectedWith but not a fulfilledWith.

I understand that I can use .to.eventually.be.fulfilled.and.equal, but I'm wondering -- are:

• .to.eventually.be.rejected.and.equal(), and
• .to.eventually.be.rejectedWith()

not essentially the same?

If so, I'd think that the fulfilledWith "shortcut" should also be included. If they're not the same, then we can close this request due to my ignorance 😄