summaryrefslogtreecommitdiffstats
path: root/tests/auto/collections
diff options
context:
space:
mode:
authorThiago Macieira <thiago.macieira@nokia.com>2009-05-19 16:10:06 (GMT)
committerThiago Macieira <thiago.macieira@nokia.com>2009-05-22 09:43:17 (GMT)
commit5a62f2add2cba756a132f94a114d770285f01d9c (patch)
tree3e736647ce7797a89b6c33a416b9a72c1b403d78 /tests/auto/collections
parent6c1d7e57ee8d7988ab9592e4112b1f28fd1d03ce (diff)
downloadQt-5a62f2add2cba756a132f94a114d770285f01d9c.zip
Qt-5a62f2add2cba756a132f94a114d770285f01d9c.tar.gz
Qt-5a62f2add2cba756a132f94a114d770285f01d9c.tar.bz2
Add an autotest to check that the network test server works
This test verifies that the network test server is behaving as expected. I think I caught all the services we need testing in the server, but there's still some work to be done: 1) verify that the FTP files are there where they're supposed to be 2) verify that FTP writable areas are writable 3) verify that the HTTP server has the correct files too 4) verify that the HTTP server requests credentials for the protected area 5) attempt to do NTLM authentication to verify the password (probably can't be done with netChat) 6) add Windows SMB tests (//qt-test-server/etc.) 7) add SQL tests (connecting to the SQL server ports) It would be good as well if we could not use QtNetwork. If you break QtNetwork, this test breaks too, so we don't know where the fault is. However, rewriting networking code will add another source of bugs (same for the NTLM authentication). Reviewed-By: João Abecasis
Diffstat (limited to 'tests/auto/collections')
0 files changed, 0 insertions, 0 deletions