* Testing
+ Daily <a href="http://www.go-mono.com/tests/index.php">test</a> results.
+
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
* System.Web/Test/TestMonoWeb : see README
* System.Web.Services/Test/standalone : see README
* System.Windows.Forms/SWFTest/
- * System.XML/Tests/System.Xml.Schema/standalone_tests : see README
+ * System.XML/Test/System.Xml/standalone_tests : see README
+ * System.XML/Test/System.Xml.Schema/standalone_tests : see README
* System.XML/System.Xml.Serialization/standalone_tests/
- * System.XML/Tests/System.Xml.Xsl/standalone_tests : see README
+ * System.XML/Test/System.Xml.Xsl/standalone_tests : see README
+ * Commons.Xml.Relaxng/Test/standalone_tests : see README
</ul>
testing.
Once all of that is done, you can do a 'make test' from the top mcs
- directory. Your test class will be automagically included in the
- build and the tests will be run along with all the others.
+ directory. Your test class needs also to be listed in the
+ .sources file at the top of the Test directory.
* Tips on writing Unit tests.
bug in their runtime or something is misleading or wrong in their
documentation. In this case, please put a detailed description of the
problem to mcs/class/doc/API-notes and do also report it to the
- <a href="mailing-lists">mailing list</a> - we'll forward this to the
+ <a href="mailing-lists.html">mailing list</a> - we'll forward this to the
Microsoft people from time to time to help them fix their documentation
and runtime.