[SOLVED] QTcpSocket successfully connects, but not to my server. What is it connecting to?

I have successfully built a thin client/server using Qt's Tcp Sockets API. I know it works very well, because I have sent plenty of data over the wire and verified it. However, my project manager wants a suite of unit-tests, and I'm implementing them using Qt's Test Library.

Anyhow, I'm trying to set up some dummy server to simply receive data from a QTcpSocket to verify a sendData() method in a unit test. When I connect the test socket, is shows that it is connected, but the slot for connecting the dummy server and its dummy socket is never called!

Can anyone see what I'm doing wrong here? ( I've stripped the code down down to just the parts that seem broken in the test class )

bq. While QTEST_MAIN creates a QApplication and runs all your tests, it does so sequentially and not with an event loop. Therefore, while your socket can indeed connect to the server (meaning qTestSocket->waitForConnected() returns true), since the app doesn't return to an event loop, the QTcpServer's signal will not get emitted, and TcpCommSocketTest::connectDummyServer() never gets called.
Try adding a call to qApp->processEvents() at the end of initTestCase(). It should let connectDummyServer() be called.

It seems that I needed to add a qApp->processEvents() call in my initialization function.

“Machines take me by surprise with great frequency.” -- Alan Mathison Turing