Qt.git - Qt s a cross-platform application framework that is used for developing application software that can be run on various software and hardware platforms with little or no change in the underlying codebase, while still being a native application with native capabilities and speed.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Update copyright year to 2011.	Jason McDonald	2011-01-11	2	-2/+2
\| \| \| \| \|	Reviewed-by: Trust Me (cherry picked from commit ac5c099cc3c5b8c7eec7a49fdeb8a21037230350)
*	Disabled tst_MakeTestSelfTest::make_check by default on mac.	Rohan McGovern	2010-06-07	1	-2/+5
\| \| \| \| \|	This test is too slow on our macs too. It's now disabled by default everywhere but Linux.
*	Skip tst_maketestselftest::make_check by default on Windows	Rohan McGovern	2010-06-04	1	-0/+3
\| \| \| \| \| \|	nmake and checktest are too slow on Windows for this test to be enabled by default. Set RUN_SLOW_TESTS=1 to run the test manually.
*	Fixed tst_maketestselftest on QWS and Windows.	Rohan McGovern	2010-06-03	3	-5/+26
\|
*	Add a test for the `make check' feature.	Rohan McGovern	2010-06-02	5	-6/+179
\|
*	Add a selftest to enforce correct test naming conventions.	Rohan McGovern	2010-03-22	2	-9/+273
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	When a test runs successfully, it outputs an XML test log, with the testcase name coming from whatever class is passed to QTest::qExec. If a test crashes, hangs, fails to compile, or otherwise fails to output a valid test log, any summary of the test results still has to display some reasonable testcase name. But we can't tell what the testcase name _would_ have been had the test run correctly - without, for example, attempting to parse the C++. The simplest solution is to make sure that TARGET and the test class name are always matching. This test will force people to follow this naming convention.
*	Make maketestselftest more strict.	Rohan McGovern	2010-03-22	1	-0/+138
\|
*	Move tests into separate .pro files, based on Qt module.	Rohan McGovern	2010-03-03	1	-14/+19
\| \| \| \| \| \| \|	Having the tests in separate projects allows for some optimization strategies when running the tests (e.g. start running corelib tests while the rest of Qt is still compiling), and allows developers to run only a subset of tests when appropriate.
*	Fixed failure of maketestselftest with vcproj generator.	Rohan McGovern	2010-02-17	1	-1/+3
\|
*	Fixed maketestselftest failure with some MSVC versions.	Rohan McGovern	2010-02-02	1	-0/+3
\| \| \| \|	The generated `tests/auto/tmp' directory was causing this test to fail.
*	Fix copyright year.	Jason McDonald	2010-01-19	1	-1/+1
\| \| \| \|	Reviewed-by: Trust Me
*	Add a selftest for tests/auto/auto.pro.	Rohan McGovern	2010-01-14	2	-0/+109
	This selftest enforces that tests/auto/auto.pro is properly maintained. It may be extended to check other elements of the environment necessary for autotests to run correctly.