zzNLM Insight Segmentation & Registration Toolkit

http://www.itk.org/HTML/Testing.htm

 

 

Testing plays a vital role in the ITK development process. The Dart testing system is used to run tests and post results on the ITK quality dashboard. The dashboard is important to developers and users alike. Developers use the dashboard to insure that code contributions function correctly across multiple hardware and software platforms, and are consistent with the existing code base. Users can view the dashboard to determine the state of the system at a particular point in time, possibly deferring a decision to update the software until the code stabilizes.

The testing dashboard is divided into several parts. The nightly builds reflect the state of the system at a particular point in time during the previous night (i.e., 9:00pm EST). The continuous builds run periodically in response to developer check-ins, and show the status of the code almost instantaneously. If errors occur during the continuous build, email is sent to the offending developer(s). Experimental builds may be submitted by anyone from any site, and are used to evaluate local changes to the software. Coverage refers to the percentage of the code that is actuallly executed. Purify is a memory-checking facility.

There are dozens of links corresponding to CVS checkins (called updates), previous days results, build warnings and erros, and the results of tests. These links can be followed to determine problems with the system, and to communicate with other developers and users.

 

 

 

CVS Statistics

http://www.itk.org/Testing/StatCVS/index.html