QCOMPARE() can report enum values by name just fine, no need to laboriously convert them to strings. While comparing all tags in one go did allow a more comprehensive report, it's enough to know we failed; this is testing cross-platform code, so a debugger can tell us all those extra details if we get a failure. Testing qHash() doesn't distinguish equal things is fairly low value; at least avoid duplicating the construction of the reference value. Replace a bunch of other QVERIFY()s with the new cousins of QCOMPARE() for ordered and different comparisons. In the process, mark some of the QLocale objects as const. Change-Id: Ic93b8ed60c6f2cc846fbba428983778896d61291 Reviewed-by: Ivan Solovev <ivan.solovev@qt.io> |
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer | ||
| manual | ||
| shared | ||
| testserver | ||
| CMakeLists.txt | ||
| README | ||
README
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.