freebsd-dev

History

nik c70ead0ed6 Switch over to a different, more flexible test output protocol that's understood by Perl's Test::Harness module and prove(1) commands. Update README to describe the new protocol. The work's broken down into two main sets of changes. First, update the existing test programs (shell scripts and C programs) to produce output in the ok/not ok format, and to, where possible, also produce a header describing the number of tests that are expected to be run. Second, provide the .t files that actually run the tests. In some cases these are copies of, or very similar too, scripts that already existed. I've kept the old scripts around so that it's possible to verify that behaviour under this new system (in terms of whether or not a test fails) is identical to the behaviour under the old system. Add a TODO file.		2004-11-11 19:47:55 +00:00
..
build	Switch over to a different, more flexible test output protocol that's	2004-11-11 19:47:55 +00:00
debugscripts	Remove vinum bits.	2004-11-04 13:34:06 +00:00
diag	For variables that are only checked with defined(), don't provide	2004-10-24 15:33:08 +00:00
kerneldoc	Experimental support for using doxygen to generate kernel documentation.	2004-07-11 16:13:57 +00:00
KSE	Follow new upcall quantum code in kernel.	2003-03-21 08:21:39 +00:00
lib32	Don't leave noschg files laying around in /tmp	2004-10-11 22:14:47 +00:00
LibraryReport
regression	Switch over to a different, more flexible test output protocol that's	2004-11-11 19:47:55 +00:00
test	For variables that are only checked with defined(), don't provide	2004-10-24 15:33:08 +00:00
tools	RELENG_5 is now -STABLE (but without powerpc)	2004-11-11 18:37:39 +00:00
install.sh	Arguments to options aren't necessarily separated with whitespace.	2004-07-07 09:38:14 +00:00
make_libdeps.sh	Teach the script where libssl actually lives.	2004-04-13 11:06:20 +00:00
README	- Add $FreeBSD$	2000-08-13 14:46:31 +00:00

README

$FreeBSD$

This directory tree contains tools used for the maintenance and
testing of FreeBSD.  There is no toplevel Makefile structure since
these tools are not meant to be built as part of the standard system,
though there may be individual Makefiles in some of the subdirs.

Please read the README files in the subdirs for further information.