mirror of
https://github.com/qt/qtmqtt.git
synced 2026-10-25 16:16:26 +00:00
45ab6b8cd2
This allows us to build manual tests together with Qt by specifying QT_BUILD_MANUAL_TESTS and QT_BUILD_TESTS. A benefit of doing this, is that the manual tests show up as debuggable targets with IDEs such as Visual Studio Code, while keeping full code navigation capabilities into the Qt code. Pick-to: 6.8 Change-Id: Idd309c06fb2586fd634386951a3345aa40bc093a Reviewed-by: Even Oscar Andersen <even.oscar.andersen@qt.io> Reviewed-by: Alexandru Croitor <alexandru.croitor@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.