e15548d3e4
Some of Qt's autotests depend on access to a test server. For each test that used the test server, tests/auto/network-settings.h created a global object to verify at startup that host lookups to the test server will succeed (and abort the test otherwise). There are two problems with that approach: First, the sanity check happens before main(), and thus before the test framework has started logging test results. This means that if the sanity check aborts the test, the failure message will not be visible in the test output if logging to a file or will cause the output to be malformed if logging to the console in XML format. Second, since Qt 4.7, the host lookup uses a class that connects to the QCoreApplication instance, which doesn't exist before main(), and this caused all tests that included network-settings.h to output an error message from QObject::connect() at the beginning of the test. Both of these problems are solved by removing the global object from network-settings.h and instead performing the sanity check in the initTestCase() function of each test. Task-number: QTBUG-22876 Change-Id: Id49c1826906327bf571686cc11527f0265e5af44 Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com> |
||
---|---|---|
.. | ||
bearerex | ||
gestures | ||
inputmethodhints | ||
keypadnavigation | ||
lance | ||
mkspecs | ||
network_remote_stresstest | ||
network_stresstest | ||
qcursor | ||
qdesktopwidget | ||
qgraphicsitemgroup | ||
qgraphicslayout/flicker | ||
qhttpnetworkconnection | ||
qimagereader | ||
qlocale | ||
qnetworkreply | ||
qssloptions | ||
qtabletevent | ||
qtbug-8933 | ||
qtouchevent | ||
qwidget_zorder | ||
repaint | ||
socketengine | ||
textrendering | ||
windowflags |