1
0
mirror of https://github.com/qt/qtmqtt.git synced 2026-10-25 16:16:26 +00:00
qtmqtt/tests
Konstantin Ritt f702420627 Tst_QMqttClient: fix the FakeServer's response regarding payload size
Change-Id: Ia4df16b8ad37c1d241b959dfc4c3194b770c7813
Reviewed-by: Maurice Kalinowski <maurice.kalinowski@qt.io>
2020-05-06 11:16:06 +00:00
..
auto Tst_QMqttClient: fix the FakeServer's response regarding payload size 2020-05-06 11:16:06 +00:00
benchmarks Make test topics unique to test class 2018-07-20 11:55:23 +00:00
common Move qWarning to categorized logging 2018-07-26 08:16:07 +00:00
libfuzzer/mqtt/data_receive Add libfuzzer test for receiving data 2019-04-18 08:13:42 +00:00
manual/sslconfiguration Add secure connection with QSslConfiguration 2019-03-04 09:02:12 +00:00
README.txt Add README for using auto tests 2018-02-02 07:59:27 +00:00
tests.pro Only build benchmarks in release mode 2017-07-24 10:48:35 +00:00

The tests included in the subdirectories check for functionality and
conformance of the Qt MQTT module.

To be able to run the tests successfully, a broker needs to be available and
reachable.

The continuous integration utilized the paho conformance test broker. It can
be obtained at this location:
https://github.com/eclipse/paho.mqtt.testing

For the unit tests being able to locate this script, use the
MQTT_TEST_BROKER_LOCATION environment variable and set it
to “<install-path>/interoperability/startbroker.py”.

Alternatively, any broker can be instantiated and passed to the auto tests
by using the environment variable MQTT_TEST_BROKER. This must point to a
valid url. The broker must run on the standardized port 1883.

Note, that the unit tests verify functionality against the MQTT 3.1.1 version
of the standard, hence the broker needs to be compliant to the adherent
specifications.