aboutsummaryrefslogtreecommitdiff
path: root/devel/libcheck/pkg-descr
diff options
context:
space:
mode:
authorMike Heffner <mikeh@FreeBSD.org>2003-12-05 00:46:02 +0000
committerMike Heffner <mikeh@FreeBSD.org>2003-12-05 00:46:02 +0000
commit600301e7c10baa7937938a47a16b196e8be2a226 (patch)
tree54ace08a6d14a2c6bbd04dd40c70420082608bb3 /devel/libcheck/pkg-descr
parent50011ebbc24e57dd4e37c7f9df7211dab7d09397 (diff)
Notes
Diffstat (limited to 'devel/libcheck/pkg-descr')
-rw-r--r--devel/libcheck/pkg-descr24
1 files changed, 24 insertions, 0 deletions
diff --git a/devel/libcheck/pkg-descr b/devel/libcheck/pkg-descr
new file mode 100644
index 000000000000..77296e616a9d
--- /dev/null
+++ b/devel/libcheck/pkg-descr
@@ -0,0 +1,24 @@
+Check is a unit test framework for C. It features a simple interface
+for defining unit tests, putting little in the way of the
+developer. Tests are run in a separate address space, so Check can
+catch both assertion failures and code errors that cause segmentation
+faults or other signals. The output from unit tests can be used within
+source code editors and IDEs.
+
+Check was inspired by similar frameworks that currently exist for most
+programming languages; the most famous example being JUnit for Java
+(www.junit.org). There is a list of unit test frameworks for multiple
+languages at www.xprogramming.com/software.htm . Unit testing has a
+long history as part of formal quality assurance methodologies, but
+has recently been associated with the lightweight methodology called
+Extreme Programming. In that methodology, the characteristic practice
+involves interspersing unit test writing with coding (" test a little,
+code a little"). While the incremental unit test/code approach is
+indispensable to Extreme Programming, it is also applicable, and
+perhaps indispensable, outside of that methodology.
+
+
+WWW: http://check.sourceforge.net
+
+- Mike
+mikeh@FreeBSD.org