Contributing To MbUnit

The MbUnit code is currently available under the Apache software license and was written by the team. Their efforts were made significantly easier by software donations from several companies and projects.

If you’d like to help us out making MbUnit even better than it already is, we’re always happy to hear from you on the MbUnit-Dev google group. We are always looking for people to help with

• The core test framework
• Our GUI and console based test runners
• MSBuild and NAnt extensions
• Documentation

Check out our Source Code

If you’d like to have a look at the MbUnit source code and docs before you join the team, you have several options. You can

• Browse the source code directly on Google Code.
• Browse the source code directly via koders.com.
• Check out a read-only working copy anonymously over HTTP with subversion. Use the following command
  

     svn checkout http://mb-unit.googlecode.com/svn/trunk/ mb-unit

Coding Guidelines

At present, we don’t have a defined set of coding standards or guidelines for the project. However

• We do use FxCop (on default settings) for checking code however, so you may want to download that for reference
• We ask that any code you submit, you also document it in the source code as well to keep this documentation set up to date.

We’ll upload a more formal set of guidelines as they are solidified.

Submitting Patches

Once you’ve had a look round the source and fixed a bug or added a new feature to your local copy, please submit it as a patch to the MbUnit-Dev list. To create a patch for SVN, use the SVN diff command like so

   svn diff changedfilename > x:\path\to\patchfile.patch

If you use TortoiseSVN, right click the files you’ve altered and choose TortoiseSVN | Create Patch... from the context menu.