qt5base-lts

History

Mitch Curtis efb283fb7f Add QTest::failOnWarning This solves the long-standing problem of not being able to easily fail a test when a certain warning is output. [ChangeLog][QtTest] Added QTest::failOnWarning. When called in a test function, any warning that matches the given pattern will cause a test failure. The test will continue execution when a failure is added. All patterns are cleared at the end of each test function. Fixes: QTBUG-70029 Change-Id: I5763f8d4acf1cee8178be43a503619fbfb0f4f36 Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>		2021-11-26 04:47:24 +01:00
..
auto	Add QTest::failOnWarning	2021-11-26 04:47:24 +01:00
baseline	Update baseline testing framework	2021-11-24 11:47:43 +01:00
benchmarks	QtBase: replace windows.h with qt_windows.h	2021-11-23 12:53:46 +08:00
global
libfuzzer	CMake: Bump almost all cmake_minimum_required calls to 3.16	2021-09-22 19:36:49 +02:00
manual	Rename and restructure the baseline (lancelot) testing code	2021-11-16 14:01:50 +01:00
shared	QtBase: replace windows.h with qt_windows.h	2021-11-23 12:53:46 +08:00
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.