Fix tests for brokers with no server connection properties

VerneMQ does not send any server connection properties at all and relies
on the default values set by the standard. All other implementations
behave differently so far, mostly to set lower limits (i.e. max packet
size).

Change-Id: I01824640021651cfe752523803b9797aed197fc9
Reviewed-by: Maurice Kalinowski <maurice.kalinowski@qt.io>

1 files changed, 1 insertions, 2 deletions

diff --git a/tests/auto/qmqttconnectionproperties/tst_qmqttconnectionproperties.cpp b/tests/auto/qmqttconnectionproperties/tst_qmqttconnectionproperties.cpp
index d592463..f08adcd 100644
--- a/tests/auto/qmqttconnectionproperties/tst_qmqttconnectionproperties.cpp
+++ b/tests/auto/qmqttconnectionproperties/tst_qmqttconnectionproperties.cpp
@@ -142,7 +142,6 @@ void tst_QMqttConnectionProperties::receiveServerProperties()
 
     QMqttServerConnectionProperties::ServerPropertyDetails properties = server.availableProperties();
     qDebug() << "Specified properties:" << properties;
-    QVERIFY(properties != 0);
 
     if (properties & QMqttServerConnectionProperties::SessionExpiryInterval)
         qDebug() << "  SessionExpiryInterval:" << server.sessionExpiryInterval();
@@ -200,7 +199,7 @@ void tst_QMqttConnectionProperties::maximumPacketSize()
             qDebug() << "Server accepts less data than required for this test.";
         }
     } else {
-        qDebug() << "Server has no max packet size specified";
+        QSKIP("Server has no max packet size defined. Default is unlimited.");
     }
 
     const QString topic = QLatin1String("Qt/ConnectionProperties/some/Topic/maxSize");