f144507829
Don't attempt the remote test if we don't have a remote server. Don't add error returns from read to byteCounter. Don't cast from ASCII to QString in URL components. Don't waste time encoding a path for which it's a no-op (especially as I recently deleted the method used to do it). Name the time-out, both for clarity and to give anyone who needs to debug the test only one line to edit so as to increase the time-out enough to make debugging practical. Change-Id: I378aa96c0501f7033ca4abb82734b03b8c807f08 Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io> |
||
|---|---|---|
| .. | ||
| auto | ||
| baselineserver | ||
| benchmarks | ||
| global | ||
| libfuzzer | ||
| manual | ||
| shared | ||
| testserver | ||
| .prev_CMakeLists.txt | ||
| CMakeLists.txt | ||
| README | ||
| tests.pro | ||
This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.
Linux X11:
* The user must be logged in to an active desktop; you can't run the
autotests without a valid DISPLAY that allows X11 connections.
* The tests are run against a KDE3 or KDE4 desktop.
* Window manager uses "click to focus", and not "focus follows mouse". Many
tests move the mouse cursor around and expect this to not affect focus
and activation.
* Disable "click to activate", i.e., when a window is opened, the window
manager should automatically activate it (give it input focus) and not
wait for the user to click the window.