Mqtt.js: Integration tests on Github Actions for all OSS brokers

Created on 28 Nov 2016  路  14Comments  路  Source: mqttjs/MQTT.js

It would be awesome to receive a contribution to do some integration testing against the major OSS brokers.

Something using Travis ENV support, or similar. It might even be a separate repo, feel free to discuss!

help wanted

Most helpful comment

Thanks @anhldbk for getting this started again.

Brokers

What to test

  • Connect

    • SSL/TLS

    • Websockets

  • Subscribe

    • QOS 0,1,2

    • Retained

  • Publish

    • Retained

  • LWT

Platform

  • Node.js
  • Browser

    • Integrationtests via SauceLabs

EDIT I am updating this list with information that are posted in the comments below..

All 14 comments

@mcollina Do we have any integration tests implemented?

zero. But I think we should.

I am on board.. Lets start with something simple like Mosca and expand from there.

I have no time to coordinate this :(. I would suggest we should start with Mosquitto and Mosca. Please go ahead and do it, I will be happy to review.

I completely agree on this. I don't have time to help right now, but I'll be happy to do so when possible.

I am trying to free some time next week.

Would you guys elaborate more on how we take integration tests? I think we should make a to-do list now. For example:

  • [ ] Listing all OSS Brokers
  • [ ] Specify what to test ...

Thanks @anhldbk for getting this started again.

Brokers

What to test

  • Connect

    • SSL/TLS

    • Websockets

  • Subscribe

    • QOS 0,1,2

    • Retained

  • Publish

    • Retained

  • LWT

Platform

  • Node.js
  • Browser

    • Integrationtests via SauceLabs

EDIT I am updating this list with information that are posted in the comments below..

Currently, I am using emq broker and find it great. It's written in Erlang (suitable for production environments).

About What to test, should we have tests for MQTT Over WebSocket?

@anhldbk I think so, yes.

It would be awesome to have integration tests also via SauceLabs.

The integration test results should be organized into a report with:

  1. Information about brokers
  2. For each broker, we should have describe the running environment. It must be reproducible. (Docker may be a great relief)
  3. Associated test scripts
  4. Finally, a summary

@sandro-k , @mcollina is that ok?

@anhldbk yes! Go ahead and make it docker-based.

Bonus points (but keep it separate): websockets in browsers.

changed the name since this is still a relevant ask but we're using Github Actions now.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

AlirezaMoseni picture AlirezaMoseni  路  4Comments

bicccio picture bicccio  路  3Comments

SSL
reejinbouk picture reejinbouk  路  4Comments

markcnunes picture markcnunes  路  7Comments

ferm10n picture ferm10n  路  5Comments