Hey, > Sounds like a plan. > > I'm a complete neophyte when it comes to contributing to mono (though > I've been using and following the project for some time), what's the > best way to submit test cases to the project?
There are a few things you will want to do: 1. Make sure you can build Mono from SVN yourself, this is so that you have all the tools in place, and you can test things. 2. Make sure you can run `xsp' on sample pages. Once you do that, I suggest that you get yourself NUnit, and write a small test case for the first class you pick (pick something easy first). You can see a bunch of samples in mcs/class/System.Web/Test/ directory. We use a file per class to test. This will help you understand the API beyond the documentation description: you will understand the inputs, the outputs, what things must be checked and what must not. Then you run this with NUnit and you make sure it works on Windows. At that point you can write your implementation for Mono. Never looking at decompiled output, never using a disassembler or any other tools but public documentation and public Microsoft blogs (avoid reverse engineering sites). Then you can contribute your tests and your classes (send us an email). Once you are comfortable with it, we give you an SVN account. > _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list