2002-04-04 Dan Lewis <dihlewis@yahoo.co.uk>

[mono.git] / web / testing

diff --git a/web/testing b/web/testing
index ca704957012f7ee493e2796545c11782660673db..f97902ec306890f7129fb36b067a56d55b57301a 100644 (file)
--- a/web/testing
+++ b/web/testing
@@ -1,4 +1,12 @@
-* Testing 
+* Testing
+
+       Testing is an important part of the Mono project: every one of its
+       three major components has a test suite tailored for its needs.  This
+       is very helpful, because in the course of developing the software it
+       is very common to introduce bugs in existing code.  A test suite
+       helps us fix the bugs as soon as they are introduced.
+
+** Class Library Tests
 
        All classes in Mono libraries should have comprehensive unit test
        suites to go with them. Unit testing is a software engineering
@@ -19,3 +27,20 @@
        more info, read <a
        href="http://junit.sourceforge.net/doc/testinfected/testing.htm">
        JUnit Test Infected: Programmers Love Writing Tests</a>.
+
+
+** Getting Started
+
+       We welcome all contributions to the Class Libary Test Suite.
+
+       There is information to help you get started in CVS at
+       mcs/class/doc/NUnitGuidelines. Once you have written your test, please
+       post it to <a href="mailing-lists.html">mono-list</a>.
+
+       Someone will make sure to add the file or apply the patch as
+       appropriate. If you plan to be an on-going contributor and
+       would like to get cvs account, email <a href="mailto:miguel@ximian.com">miguel</a>.
+
+       Normally, after you send a couple of well-written new files
+       and/or patches to the list, you will be given cvs access.
+