web site updates

[mono.git] / web / testing

diff --git a/web/testing b/web/testing
index 424d6387cd62fd1d201f68b995a43225c65416f1..f97902ec306890f7129fb36b067a56d55b57301a 100644 (file)
--- a/web/testing
+++ b/web/testing
@@ -1,24 +1,46 @@
-* 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
        methodology that makes it easier to build correct code. Every
        method in every class should have a set of tests to verify
-       they work correctly. Mono also needs a testing framework to
-       make it easy to write and run lots of tests. <a
-       href="http://www.junit.org/">JUnit</a>
-       and its spinoffs (collectively, <a
-       href="http://www.xprogramming.com/software.htm">XUnit</a>)
-       are a well designed framework for building unit
-       tests. Implementing JUnit in Mono is a first priority.
+       that they work correctly. Mono also needs a testing framework
+       to make it easy to write and run lots of tests. 
+
+       Try <a href="http://nunit.sourceforge.net">NUnit</a>
 
        Why do unit testing? It becomes simple to run automated tests
        for the whole library. Unit tests are a safety net - you can
        change part of the code and verify that you haven't broken
        anything. Ideally, tests are written before the actual library
        code itself. And every time a bug is discovered, a test should
-       be written to demonstrate the bug, fix the bug, and then if
-       you ever reintroduce the bug you will know immediately. For
+       be written to demonstrate the bug and its fix. Then, if
+       you ever reintroduce the bug, you will know immediately. For
        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.
+