blob: 15c87abdd4e29696988de332692b35a106c2114e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
[[!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]], [[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:
* <http://www.codesourcery.com/public/qmtest/whitepaper.pdf>
* <http://www.python.org/workshops/2002-02/papers/01/index.htm>
* <http://gcc.gnu.org/ml/gcc/2002-05/msg01978.html>
* <http://www.codesourcery.com/public/qmtest/qmtest-snapshot/share/doc/qmtest/html/tutorial/index.html>
* <http://www.codesourcery.com/public/qmtest/qmtest-snapshot/share/doc/qmtest/html/manual/index.html>
|
