path: root/tests/
Commit message (Collapse)AuthorAgeFilesLines
* iOS: Enable building of basic testsTor Arne Vestbø2014-01-221-1/+1
| | | | | | | Allows us to sanity check the iOS build in the CI. Change-Id: I16f9bfafef3988dcab6efd3155503ca0d0b4d1d8 Reviewed-by: Morten Johan Sørvig <>
* Properly implement a 'make docs' target for subdirs and apps/libsMarius Storm-Olsen2012-05-091-0/+1
| | | | | | | | | | | | | | Only call qdoc for projects which sets the QMAKE_DOCS variable to point to a qdocconf file. Exclude examples/ and tests/ from the qdoc run, by adding no_docs_target to CONFIG for those projects. Change-Id: Ic856c8f19db59309302d0602b3e99735609e525a Reviewed-by: Lars Knoll <> Reviewed-by: Oswald Buddenhagen <> Reviewed-by: Casper van Donderen <>
* Re-enable the corelib autotests on Mac OS XBradley T. Hughes2011-11-211-3/+0
| | | | | | | | | | | | | | | | | | | This is the first change to re-enable the autotests for the individual qtbase modules. This means adding subdir.CONFIG=no_check_target for each module (except corelib) in tests/auto/ instead of in tests/ QFileSystemWatcher, QIODeice, QSettings, QTextStream, QSocketNotifier, QVariant, QPluginLoader, QLocale: These tests currently fail, which will block any changes that attempt to re-enable the autotests. Ignore the failures for now by marking them as insignificant. QAbstractItemModel: This test currently crashes, which can destabilize the CI system when attempting to re-enable the autotests. Skip this test for now by disabling the check target for it. Change-Id: Ie5147d5c5cfae5e7d0a495d5c4788ce92fe2e6d8 Reviewed-by: Marius Storm-Olsen <>
* Build all tests on Mac OS X, but do not run them yet.Bradley T. Hughes2011-11-171-2/+3
| | | | | | | | | | | | | | Previously, autotests and benchmarks were disabled on Mac OS X. This is wrong, and needs to be corrected. The 'make check' target is disabled for the autotests on Mac OS X for now, but all tests will now be built. The check target does not actually run the benchmarks, so this can be safely re-enabled without breaking the CI system. There will be commits to follow which re-enable the 'make check' target on Mac OS X for each module. Change-Id: I1347da46e3688b48e8cc5d933ee5188ea3723639 Reviewed-by: Rohan McGovern <>
* Integrate testcocoon support into Qt build system.Rohan McGovern2011-11-151-1/+2
| | | | | | | | | | | | To instrument a Qt application or library with the TestCocoon coverage tool, do `CONFIG+=testcocoon' in the application .pro file. To instrument Qt itself with testcocoon, use the `-testcocoon' configure option. Change-Id: Ie77109a078d11ea51f7a073621e0df9c752c44ae Reviewed-by: Oswald Buddenhagen <> Reviewed-by: Rohan McGovern <>
* disable autotests temporarily on MacLars Knoll2011-09-141-0/+2
| | | | | | Reviewed-By: Morten Change-Id: Iaf404deb3dd226212200a8716f8e7d1b70e5f40a
* Don't attempt to build benchmarks if release-mode Qt is not availableRohan McGovern2011-06-211-2/+4
| | | | | | | | | | | | | | | All of the benchmarks explicitly turn on release mode. This fails on Mac and Windows if Qt is configured as debug-only. It is also possibly misleading on Linux, as compiling the benchmark in release mode does not imply that Qt is compiled in release mode. The results are generally not useful if release mode Qt is not available, so disable them by default in this case. Change-Id: Ifa2bb6ab6412dd360ff9dfb890ace2f51e0eef86 Reviewed-on: Reviewed-by: Qt Sanity Bot <> Reviewed-by: Jo Asplin <>
* Initial import from the monolithic Qt.Qt by Nokia2011-04-271-0/+3
This is the beginning of revision history for this module. If you want to look at revision history older than this, please refer to the Qt Git wiki for how to use Git history grafting. At the time of writing, this wiki is located here: If you have already performed the grafting and you don't see any history beyond this commit, try running "git log" with the "--follow" argument. Branched from the monolithic repo, Qt master branch, at commit 896db169ea224deb96c59ce8af800d019de63f12