summaryrefslogtreecommitdiffstats
path: root/tests/auto/qsocketnotifier/qsocketnotifier.pro
Commit message (Collapse)AuthorAgeFilesLines
* Fix crash when QSocketNotifier used with an invalid descriptorShane Kearns2011-04-211-1/+1
| | | | | | | | | | | | | select code for open C file/socket descriptors was crashing in FD_SET if a QSocketNotifier was created with an invalid descriptor. Added two autotests to QSocketNotifier, one to check notifiers with bogus socket descriptors don't crash, the other to check that notifiers with posix socket descriptors do work. (symbian socket engine doesn't use them so they are not implicitly tested) Reviewed-by: mread Task-Number: QTBUG-18138
* Run autotests with minimal capabilitiesShane Kearns2010-05-101-0/+1
| | | | | | | | | | | The autotests were previously run with ALL-Tcb capability which gives them more access to the filesystem etc. than a typical Qt application. To have more realistic testing environmnent, tests are run with no capabilities other than those required for the Qt APIs they use. i.e. NetworkServices for network tests, None for others. Reviewed-by: Liang Qi
* Disable private unit tests when Qt is configured withoutRohan McGovern2009-07-091-0/+2
| | | | | | | | | | | | -developer-build, part 2. Some autotests use private (unexported) code, either because they're testing private classes or because that's the easiest way to test the public classes. Configuring Qt with `-developer-build' is needed for these tests. This commit fixes the tests so configuring without `-developer-build' only builds the tests which strictly use public API.
* Long live Qt!Lars Knoll2009-03-231-0/+8