hero123457/qtmqtt
1
0
Fork 0
mirror of https://github.com/qt/qtmqtt.git synced 2026-10-25 16:16:26 +00:00
Code Issues Projects Releases Wiki Activity
b9ac8d04f2
qtmqtt/tests
History
Maurice Kalinowski b9ac8d04f2 MQTT5: Rename QMqttServerConnectionProperties::reasonString 
Use reason() as name for consistency with other cases.

Change-Id: I9219a0fd47520f10f1c4b85fd0c4428dcc2d39a1
Reviewed-by: hjk <hjk@qt.io>
2018-08-09 10:30:17 +00:00
..
auto MQTT5: Rename QMqttServerConnectionProperties::reasonString 2018-08-09 10:30:17 +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
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

README.txt 

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.