Skip to content

Conversation

danielpeintner
Copy link
Member

fixes #1299

).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...
Copy link
Member Author

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?

@danielpeintner
Copy link
Member Author

Note: I fixed some easy issues and skipped tests that fail now in

  • core
  • http
  • mqtt

I added information/questions in the commit/changes.

Please have a look.

@danielpeintner danielpeintner marked this pull request as draft July 8, 2024 16:20
should();

describe("MQTT client implementation - integration", () => {
describe.skip("MQTT client implementation - integration", () => {
Copy link
Member Author

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
@danielpeintner
Copy link
Member Author

Question: Should we re-vice this PR to get a stricter policy

@relu91
Copy link
Member

relu91 commented Sep 8, 2025

Are there still issues with the MQTT tests?

@danielpeintner
Copy link
Member Author

Are there still issues with the MQTT tests?

Yes, there are MQTT issues, but there are also test issues with HTTP and core.
Please take a look at the changes.

I fixed on obvious HTTP test bug, but I skipped some more in core also where I am not sure about...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[test] Convert unhandledRejection to uncaughtException
2 participants