diff options
| author | Miguel de Icaza <miguel@gnome.org> | 2001-07-06 04:22:40 +0400 |
|---|---|---|
| committer | Miguel de Icaza <miguel@gnome.org> | 2001-07-06 04:22:40 +0400 |
| commit | 3d6ecf40664c0e72e250e1628289279c2859b98a (patch) | |
| tree | 1fa4a0cbadb04e877c9643d06877d5a4dd2e9e80 /web/testing | |
| parent | 5a8951e8cffbf86de06718cd859c83f6005786d9 (diff) | |
Update FAQ
svn path=/trunk/mono/; revision=54
Diffstat (limited to 'web/testing')
| -rw-r--r-- | web/testing | 9 |
1 files changed, 3 insertions, 6 deletions
diff --git a/web/testing b/web/testing index 424d6387cd6..ba0bf921592 100644 --- a/web/testing +++ b/web/testing @@ -5,12 +5,9 @@ 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. + 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 |