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
As mentioned in #1298 by @relu91 (see here #1298 (comment)) mocha ignores the new nodejs mechanism of reporting async unhandled exceptions.
We need to set mocha --unhandled-rejections=strict --require ts-node/register --extension ts in all package.json files.
mocha --unhandled-rejections=strict --require ts-node/register --extension ts
Doing so for binding-http shows already some issues. see #1298 (comment)
binding-http
plus: we also might want to rework the test introduced in #1298 by simply doing something like (await text(data.body)).should.eql("Test event");
(await text(data.body)).should.eql("Test event");
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
As mentioned in #1298 by @relu91 (see here #1298 (comment)) mocha ignores the new nodejs mechanism of reporting async unhandled exceptions.
We need to set
mocha --unhandled-rejections=strict --require ts-node/register --extension ts
in all package.json files.
Doing so for
binding-http
shows already some issues.see #1298 (comment)
plus: we also might want to rework the test introduced in #1298 by simply doing something like
(await text(data.body)).should.eql("Test event");
The text was updated successfully, but these errors were encountered: