[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] A collection of thoughts with respect to unit testing. We definitely want to add unit test suites to our code base. We should select a tool that we like to use, and that is supported (not abandoned). * [DejaGnu](http://www.gnu.org/software/dejagnu/) / [Expect](http://expect.nist.gov/) * used by the [[GCC testsuite|gcc]], [[GDB_testsuite]], [[binutils testsuite|binutils/testsuite]], etc. * The [[glibc_testsuite]] has a home-grown system (Makefile-based), likewise does the [[Open_POSIX_Test_Suite]]. * [check](http://check.sourceforge.net/) * used by some GNU packages, for example GNU PDF (Jose E. Marchesi) * CodeSourcery's [QMTest](http://www.codesourcery.com/qmtest) * useb by? * documentation: * * * * * * [*[ANNOUNCE] ktest.pl: Easy and flexible testing script for Linux Kernel Developers*](http://lwn.net/Articles/412302/) by Steven Rostedt, 2010-10-28. [v2](http://lwn.net/Articles/414064/), 2010-11-08. # Related * [[nightly_builds]] * [[nightly_builds_deb_packages]] * -- ``comprehensive testing and benchmarking platform''. This one might be useful for [[performance]] testing, too? *