Golden Rules
Here are some rules that we follow when developing jMock:
- Test Driven: Never check in a class without associated unit tests.
- Unit Tests Always Pass: Never check a failing unit test into the CVS repository.
- Acceptance Tests Can Fail: A failing acceptance test indicates something that needs to be done: a todo item, feature request or bug report, for example. It's ok to check a failing acceptance test into the CVS repository.
- Separate Acceptance and Unit Tests: Make it easy to run only the unit tests so that we can check that they pass before committing, even when acceptance tests are failing.
Conventions
We follow Sun's coding conventions for Java.
We use the TestDox1 naming conventions for unit tests.
Development Resources
The team2 have written the following documents about development of jMock.
| How to contribute3 | Instructions on how to contribute to the project. We welcome all sorts of contributions including patches, code, documentation, bug reports and feature requests. |
|---|---|
| The Team2 | About the people responsible for jMock. |
Project Reports
The continuous build process produces the following reports:
| Build Status4 | The status of the current continuous integration build, a history of builds and build logs. |
|---|
News Feeds
You can subscribe to the following feeds to keep track of development activity
Links:
1. http://agiledox.sourceforge.net/
2. http://www.jmock.org/team.html
3. http://www.jmock.org/how-to-contribute.html
4. http://beetlejuice.codehaus.org/beetlejuice/viewProjectSummary.action?projectName=jMock
5. http://cvs.jmock.org/changelog/~rss,/jmock/rss.xml
6. http://beetlejuice.codehaus.org/beetlejuice/jMockBuilds.xml
7. http://beetlejuice.codehaus.org/beetlejuice/jMockFailedBuilds.xml