Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/mono/mono.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAaron Weber <aaron@mono-cvs.ximian.com>2001-07-08 02:23:21 +0400
committerAaron Weber <aaron@mono-cvs.ximian.com>2001-07-08 02:23:21 +0400
commit25b5d7a7ff00b6ab4ce35d7604f4e45801791b85 (patch)
treedccebd348f7f48b474fc4253e4f158087dcc4bc9 /doc/testing
parent4ba499dd3119a08c717effca3812cfeac4a3bb84 (diff)
2001-07-07 Aaron Weber <aaron@ximian.com>
* doc/thanks: style, grammar. (FIXME: "a to read"? clarify) * doc/testing style, grammar. * doc/status: same. * doc/runtime: same. * doc/resources: same. * doc/rationale: same. * doc/ideas: same. * doc/gcc-frontend: same. (FIXME: clarify) * doc/faq: same. (FIXME: merge w/cheridy's version) * doc/documentation: same. * doc/class-library: same. * doc/index: same. svn path=/trunk/mono/; revision=67
Diffstat (limited to 'doc/testing')
-rw-r--r--doc/testing8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/testing b/doc/testing
index ba0bf921592..ca704957012 100644
--- a/doc/testing
+++ b/doc/testing
@@ -4,8 +4,8 @@
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.
+ 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>
@@ -14,8 +14,8 @@
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>.