Here are some ways in which stakeholders can contribute to the Watir Project:

1. Submit a Patch
   • Unit Tests
     It is suggested that the test developer uses Test Driven Development(TDD). This is where the developer creates a unit test first and then develops production code to make that unit test pass. It is an iterative and incremental way of creating software that helps the creator focus on design, areas that could go wrong; provides provability and gives the user of that software an indication of how to use that software. A good reference for TDD (although using Java) is Jeff Langr's 'Agile Java' http://www.langrsoft.com/ourBooks.shtml ; there are also examples on the aforementioned site.

1. • Tortoise SVN Client (paraphrased from http://www.io.com/~wazmo/blog/archives/2006_09.html#000241
     Tortoise SVN is a third-party client for the Subversion version control system. Once Tortoise SVN is installed goto the location in Windows Explorer where Watir is to be installed and checkout from this location: http://svn.openqa.org/svn/watir/trunk/watir. When changes have been made select the working directory, right click and choose "TortoiseSVN > Create Patch" (don't forget your unit tests).

1. • Eclipse
     There is a Subversion Eclipse Plugin called: Subclipse . Instructions on how to submit a SVN patch using it are here .

1. • Manual Submission
     It would be a good idea to put Watir code under personal source control before changes are made. However, if source control is not used contributors can send the Watir development team their modified version (wtr-development@rubyforge.org), but they must state the version of Watir that was used as the baseline and include the original and changed versions of the code.

Here is a good article that describes how to create a patch.