-
Notifications
You must be signed in to change notification settings - Fork 88
refactor: update mocha tests with --unhandled-rejections=strict #1300
New issue
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
base: master
Are you sure you want to change the base?
Conversation
).to.eventually.be.rejectedWith(Error); */ | ||
|
||
// TODO need to be fixed, call above works fine, reports true | ||
// should we really fail if uri Variable is not supported/known? I don't think so... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the actual question. Shall we really fail?
Note: I fixed some easy issues and skipped tests that fail now in
I added information/questions in the commit/changes. Please have a look. |
should(); | ||
|
||
describe("MQTT client implementation - integration", () => { | ||
describe.skip("MQTT client implementation - integration", () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@egekorkan can you check the MQTT tests which I skipped?
# Conflicts: # packages/td-tools/package.json
Question: Should we re-vice this PR to get a stricter policy |
Are there still issues with the MQTT tests? |
Yes, there are MQTT issues, but there are also test issues with HTTP and core. I fixed on obvious HTTP test bug, but I skipped some more in |
fixes #1299