We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extracted form the discussion of #47.
#47 (comment)
* If #45 lands, then expand `verify` to ensure all promises from `resolves` and `rejects` are resolved or rejected
The following example will pass, because we don't let the test runner handle the returned promise.
describe("some test", function() { it("should resolve", function() { referee.assert.resolves(Promise.resolve(42), 43); }): });
This issue is an approach to verify if all async assertions have been properly resolved.
@mroderick, @mantoni
The text was updated successfully, but these errors were encountered:
Go for it!
Sorry, something went wrong.
@mgred, if you are not looking into this, I can give it a try.
I don't think they'll be too upset if your work overlaps ... and after six months, I think it's fair to take it up 👍
@mroderick , Thanks. I will look into this.
mgred
No branches or pull requests
Extracted form the discussion of #47.
#47 (comment)
The following example will pass, because we don't let the test runner handle the returned promise.
This issue is an approach to verify if all async assertions have been properly resolved.
@mroderick, @mantoni
The text was updated successfully, but these errors were encountered: