Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | tests: Re-enable tst_MacGui test. | Sergio Ahumada | 2012-07-16 | 1 | -2/+0 |
| | | | | | | | | | The test has one stable failure. Mark this with QEXPECT_FAIL and re-enable the test. Task-number: QTBUG-26514 Change-Id: I6faeda44224f2010ed836425a787269bfe483168 Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com> | ||||
* | tests: allow unstable tests to be marked with CONFIG+=insignificant_test | Sergio Ahumada | 2011-12-28 | 1 | -0/+1 |
| | | | | | | | | | | Marking a test with CONFIG+=insignificant_test will cause the exit code of the test to be discarded during `make check'. This is intended to be used for tests which are valuable to run, but are known to be unstable and are not feasible to immediately fix. Change-Id: Id7b2407d0a13c8de19a58badb78fa7c018c9b50a Reviewed-by: Jo Asplin | ||||
* | Cleaned up test naming and platform-specific tests. | Rohan McGovern | 2009-08-06 | 1 | -7/+3 |
| | | | | | | | | | | | | | | When an autotest fails to compile, there's no way to determine which testcase(s) have been prevented from running. Our results parsing tools have been guessing, under the assumption that a directory called `qdogwalker' always contains a testcase named `tst_qdogwalker'. That wasn't true for all our tests, so let's make it true. Also changed the platform-specific tests so that qmake will simply skip those tests on unsupported platforms, instead of wasting time compiling a useless QTEST_NOOP_MAIN test. | ||||
* | Long live Qt 4.5! | Lars Knoll | 2009-03-23 | 1 | -0/+15 |