Even Oscar Andersen 8316766cec Add tests for websocket support for mqtt ... For at least one platform run the twelve combinations of: Transport: [Tcp,Ssl,Ws,Wss] Protocol: [3.1, 3.1.1, 5.0] This happens if the following defines are present: MQTT_TEST_BROKER MQTT_TEST_TYPE MQTT_TEST_PROTOCOL If these are not defined, the old test behavior is kept The logic is that we are replacing the type of VersionClient to homegrown logic that replaces connectToHost with the correct function: connectToHost connectToHostEncrypted, connectToHostWebSocket connectToHostWebSocketEncrypted For this to work it is important that the VersionClient macro is used everywhere. Also, DefaultVersionTestData has been changed to return version(0) if MQTT_TEST_PROTOCOL is defined, we will now run one protocol at the time instead. This is Change Request 2 of 2 wrt testing. Task-number: QTBUG-129171 Change-Id: I4f68d7c2ea226a1107f009c80f87f8b749d9f120 Reviewed-by: Jøger Hansegård <joger.hansegard@qt.io>		2025-01-29 15:54:55 +01:00
..
qmqttclient	Add tests for websocket support for mqtt	2025-01-29 15:54:55 +01:00
benchmarks.pro	Move stressTests to benchmarks	2017-04-27 13:57:06 +00:00