summaryrefslogtreecommitdiffstats
path: root/Tests/CMakeLists.txt
Commit message (Collapse)AuthorAgeFilesLines
* Add a high COST value to BootstrapTest so that it will be scheduled first in ↵Zach Mullen2010-02-111-0/+2
| | | | parallel ctest executions.
* Re-enabled Scheduler test and fixed the underlying problem.Zach Mullen2010-02-031-10/+10
|
* Disable Scheduler test until underlying problem is resolved.Zach Mullen2010-02-031-10/+10
|
* Add unit test to ensure that CTestCostData scheduling works correctlyZach Mullen2010-02-031-0/+11
|
* Fix BadExe test on cygwin.Bill Hoffman2009-12-181-6/+8
|
* Test the CheckTypeSize moduleBrad King2009-12-171-0/+2
| | | | | We create test "Module.CheckTypeSize" to verify that type sizes get detected correctly.
* Teach ADD_TEST_MACRO about test namespacesBrad King2009-12-171-4/+6
| | | | | | We teach ADD_TEST_MACRO to transform names of the form "Namespace.Name" to the directory "Namespace/Name" and the project name "Name". This will allow new tests to be better organized.
* Workaround for CTestTestBadExe on CygwinZach Mullen2009-12-171-2/+6
|
* Add a test to build the CSE project if the optional cache entry ↵David Cole2009-12-151-0/+13
| | | | CMAKE_TEST_PROJECT_CSE_DIR is set.
* Add one more possible error message from curl for the failed submit tests.David Cole2009-12-151-0/+1
|
* Test FortranCInterface flag propagationBrad King2009-12-141-0/+9
| | | | | | We create test FortranC.Flags to try passing per-language flags from a project into its FortranCInterface detect/verify checks. We wrap the compilers with scripts that enforce presence of expected flags.
* New decision method to enable Fortran testsBrad King2009-12-101-14/+5
| | | | | | | | | | CMake does not enable Fortran for its own build, but it needs to find a Fortran compiler to know if it is possible to enable Fortran tests. Previously we searched for a hard-coded list of Fortran compilers which was duplicated from the CMakeDetermineFortranCompiler.cmake module. We now run CMake on a small test project that enables the Fortran language and reports the compiler it found. This represents a more realistic check of whether the Fortran tests will be able to find a compiler.
* Test 'install' target of CMake itselfBrad King2009-12-101-0/+2
| | | | | | We create option CMake_TEST_INSTALL to enable a new CMake.Install test. It tests running the "make install" target to install CMake itself into a test directory. We enable the option by default for dashboard builds.
* Apply CMake test-time config to all testsBrad King2009-12-101-4/+0
| | | | | | We configure an EnforceConfig.cmake script to load at CTest time. Previously we loaded it from Tests/CTestTestfile.cmake, but now we load it from the top level so it applies to all tests.
* Create CMakeLib test driver and test cmXMLParserBrad King2009-12-081-0/+2
| | | | | We create a new CMakeLibTests driver executable in which to writes unit tests for CMakeLib. Our first test is a smoke-test of cmXMLParser.
* Remove WILL_FAIL property from BadExe test, since CTest was returning 0. ↵Zach Mullen2009-12-071-1/+2
| | | | Replaced with a pass regex.
* Added a unit test for running a test command which exists but is not an ↵Zach Mullen2009-12-071-0/+10
| | | | executable, because it previously caused the outer ctest process to fail.
* Fix issue #2336 - honor the -C arg to ctest. Honor it for all stages of ↵David Cole2009-12-041-4/+48
| | | | running -D dashboards from the command line and running ctest_configure, ctest_build and ctest_test commands in -S scripts. Also, allow a script to change it by setting the CTEST_CONFIGURATION_TYPE variable: allows for multiple configuration build/test cycles within one script. Add a new signature for the cmake command build_command that accepts CONFIGURATION as one argument. The original build_command signature is still there, but now marked as deprecated in the documentation. Of course... also add CTestConfig tests to verify that -C is honored for -D dashboards and -S scripts.
* Always use a configuration for CTestTestTimeoutBrad King2009-12-011-1/+7
| | | | | | | | This test requires that the dashboard script it drives be invoked with "ctest -C <config> -S ...". We create a "CTestTest_CONFIG" variable to hold a configuration selected at test time. We use the configuration given to the outer CTest, if any, and then default to either Debug or the CMAKE_BUILD_TYPE.
* CTest: Test process tree kill on timeoutBrad King2009-11-301-1/+2
| | | | | | | | | | | We extend the CTestTestTimeout test to check that when a test times out its children (grandchildren of ctest) are killed. Instead of running the timeout executable directly, we run it through a cmake script that redirects the timeout executable output to a file. A second test later runs and verifies that the timeout executable was unable to complete and write data to the log file. Only if the first inner test times out and the second inner test passes (log is empty) does the CTestTestTimeout test pass.
* Cleanup CMakeBuildTest in test_clean targetBrad King2009-11-301-0/+1
| | | | | The test_clean target is supposed to remove all test build directories. We add the build directory for CMakeBuildTest because it was missing.
* Improve fake $HOME test isolation codeBrad King2009-11-241-0/+9
| | | | | | | | | | | | | The commit "Fake $HOME to isolate tests from user" started setting $HOME in the CTest script environment. On some platforms tests depend on some local configuration in the home directory, such as the "cvs login" for KWSys in CTestTest3. In this commit we now construct a fake home dir during CMake config step and populate it with a .cvspass file needed by the test. We also check CTEST_NO_TEST_HOME to optionally disable the test home. See issue #9949.
* Test CMP0015 OLD and NEW link_directories behaviorBrad King2009-11-241-0/+1
| | | | | We create a LinkDirectory test to check that the policy OLD and NEW behaviors work as documented. See issue #9697.
* BUG 9950: increase timeout for BootstrapTest to 1.5 hoursZach Mullen2009-11-231-1/+1
|
* SimpleInstall test now builds an installer package if CTEST_TEST_CPACK is ON ↵David Cole2009-11-161-0/+1
| | | | at the Tests/CMakeLists.txt level.
* Change logic of ctest subdirs command to allow for absolute paths. Also ↵Zach Mullen2009-11-101-0/+3
| | | | added test coverage for passing absolute paths to subdirs.
* Fix TRY_RUN cross compile test to pass consistentlyZach Mullen2009-11-091-0/+2
|
* Added test coverage for TRY_RUN in cross compile mode.Zach Mullen2009-11-091-0/+1
|
* Add missing depend because of registry write with complex name, they can not ↵Bill Hoffman2009-11-041-0/+2
| | | | be done in parallel.
* Fix failed submit test 'failures'... Regular expression now matches ↵David Cole2009-10-301-2/+2
| | | | [Cc]ouldn't and [Cc]ould not.
* Fixed CTestTestRunScriptZach Mullen2009-10-291-4/+4
|
* Backout RunScript test again... (debugging on faraway)Zach Mullen2009-10-291-4/+4
|
* Fix RunScript test; it should now work on all platformsZach Mullen2009-10-291-4/+4
|
* Increase timeout for the nightly build tests so that the poor mac nightly ↵David Cole2009-10-281-1/+1
| | | | build on dashmacmini2 might have enough time to complete successfully. Use CMAKE_LONG_TEST_TIMEOUT instead of a hard-coded number for the test TIMEOUT property so that a calling script may adjust it by setting a higher CTEST_TEST_TIMEOUT value.
* Increase timeout for the nightly build tests so that the poor mac nightly ↵David Cole2009-10-281-1/+1
| | | | build on dashmacmini2 might have enough time to complete successfully. Allow for up to 3 hours. After measuring successful runs for a few weeks, perhaps we can use a lower value.
* Changed RunScript test to be in-source build safeZach Mullen2009-10-281-2/+2
|
* Test per-config OUTPUT_DIRECTORY propertiesBrad King2009-10-281-0/+1
| | | | | | | We test (ARCHIVE|LIBRARY|RUNTIME)_OUTPUT_DIRECTORY_<CONFIG> properties by building COnly as a subdirectory and setting the properties to put its files in specific locations. We build an executable that verifies the targets actually appear where expected.
* Add test CMakeTestBadCommandLines. Also add --graphviz arg to cmake invoked ↵David Cole2009-10-271-0/+16
| | | | during the CPackComponents test. The purpose of each is to increase coverage of cmake.cxx.
* Add test to enable detecting differences between generation N and N+1 of a ↵David Cole2009-10-261-0/+15
| | | | cmake generated build tree. Theoretically, each generation run with exactly the same arguments should be identical to the previous generation... Practically, there are differences. This is a tool to help us measure those differences. For now, the test always succeeds. Eventually, we may add the code to make it fail when there are differences.
* Disable run_script test for now, it is failing currently on linuxZach Mullen2009-10-261-4/+4
|
* Added test coverage for cmCTestRunScriptCommandZach Mullen2009-10-261-0/+13
|
* Add a ctest test to cover cmCTestBatchTestHandler. Since its behavior isn't ↵Zach Mullen2009-10-261-2/+3
| | | | fully defined yet, we just run it as is and don't care much about the result.
* Turn on the NSIS binary for the CPackComponents test if NSIS is found. ↵David Cole2009-10-251-4/+9
| | | | Should increase coverage of the NSIS generator on the dash16 coverage dashboard.
* Add test of all cmake -G generators. Ignore any errors from this as not all ↵David Cole2009-10-221-0/+14
| | | | generators are expected to be usable on all machines. Help to increase coverage of the various generators and cmake.cxx itself.
* Test OSX_ARCHITECTURES target propertyBrad King2009-10-211-2/+10
| | | | | | | We test the property with a project that fails to link due to an architecture mismatch between an executable and a static library. See issue #8725.
* Add test of all available CPack generators. Add this test with the goal of ↵David Cole2009-10-201-0/+34
| | | | increasing coverage of the cpack source code, even/especially when the underlying packager tool is not installed. The test does not fail if there is a cpack problem with a certain generator. I expect some generators will fail on every machine running a CMake dashboard.
* Added a ctest add_subdirectory test which fails before my patch made earlier ↵Zach Mullen2009-10-201-0/+9
| | | | today.
* Allow test to pass even if an expected-to-fail submit claims 'Submission ↵David Cole2009-10-161-1/+2
| | | | successful' - apparently when there is a valid HTTP_PROXY involved, our submitting to an empty drop location appears to succeed. Presumably, the proxy simply takes it like a man, and then discards it...
* add a test which checks that cmake can build the latest stable KDE4 ↵Alexander Neundorf2009-10-151-0/+42
| | | | | | | | | | | (kdelibs) release To enable this test, the option TEST_KDE4_STABLE_BRANCH must be switched on. It can only be switched on if CMAKE_RUN_LONG_TESTS is ON. Then the test will only be added if Qt >= 4.5 can be found, Perl can be found and ZLIB can be found. Alex
* Use LABELS in some ctest_coverage calls to increase coverage in ↵David Cole2009-10-151-0/+11
| | | | cmCTestCoverageHandler.cxx.
generated by cgit v0.12 at 2025-01-31 04:45:42 (GMT)