Difference between revisions of "CTestSummary"
| Line 1: | Line 1: | ||
== Description and Documentation== | == Description and Documentation== | ||
| − | CTest is a testing tool distributed as part of [[CmakeSummary|CMake]]. | + | CTest is a testing tool distributed as part of [[CmakeSummary|CMake]]. It serves as a client to the DART test server. CTest's role is to control the execution of tests and push the results to DART. DART then displays the results of these tests on the testing dashboard. Projects that are configured with CMake are easily tested with CTest. |
| + | |||
| + | CTest and DART form the core of the NAMIC test-driven development (TDD) process. This process facilitates agile programming by supporting a continuous feedback look between user, developers and test results. As the this figure shows, CTest is used to test code found in a source code repository (i.e., CVS or SVN), push the results to DART, where the results are viewed by developers possibly distributed around the world. Developers then make corrections to code or necessary modifications to insure that the dashboard stays "green" and the code quality stays high. | ||
| + | |||
| + | A rigorous testing process such as that practiced by NAMIC is critical to the stability and robustness of software systems. Without continuous testing, changes introduced into the system can easily introduced unanticpated side effects and/or bugs. | ||
| + | |||
| + | |||
| + | Additional usage details for it can be found [http://www.cmake.org/Wiki/CMake_Testing_With_CTest here]. | ||
Revision as of 00:57, 15 April 2007
Home < CTestSummaryDescription and Documentation
CTest is a testing tool distributed as part of CMake. It serves as a client to the DART test server. CTest's role is to control the execution of tests and push the results to DART. DART then displays the results of these tests on the testing dashboard. Projects that are configured with CMake are easily tested with CTest.
CTest and DART form the core of the NAMIC test-driven development (TDD) process. This process facilitates agile programming by supporting a continuous feedback look between user, developers and test results. As the this figure shows, CTest is used to test code found in a source code repository (i.e., CVS or SVN), push the results to DART, where the results are viewed by developers possibly distributed around the world. Developers then make corrections to code or necessary modifications to insure that the dashboard stays "green" and the code quality stays high.
A rigorous testing process such as that practiced by NAMIC is critical to the stability and robustness of software systems. Without continuous testing, changes introduced into the system can easily introduced unanticpated side effects and/or bugs.
Additional usage details for it can be found here.
