mirror of
https://github.com/qt/qtmqtt.git
synced 2026-10-25 16:16:26 +00:00
fb417c44dd
A topic can have multiple '+' wildcards, but isValid was searching for the wrong wildcard at the second instance. Pick-to: 6.6 6.5 6.2 Change-Id: I83e3fa258ef01b26388c0e6fd8c17a0a140ab75a Reviewed-by: Karsten Heimrich <karsten.heimrich@qt.io> |
||
|---|---|---|
| .. | ||
| auto | ||
| benchmarks | ||
| common | ||
| libfuzzer/mqtt/data_receive | ||
| manual | ||
| CMakeLists.txt | ||
| 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.