Golden Rules
Here are some rules that we follow when developing JBehave:
- Example Driven: Only create code to solve a realistic (and preferably real) problem.
- Behaviour Driven: Only create classes once you can describe and automate examples of their behaviour.
- No Misbehaving: Automated examples must work before being checked into the repository, and existing tests must not be broken.
Development Resources
The team have written the following documents about development of JBehave.
- How to contribute : Instructions on how to contribute to the project. We welcome all sorts of contributions including patches, code, documentation, bug reports and feature requests.
- The Team : About the people responsible for JBehave
Project tools
- Bamboo JBehave : Continuous Integration Builds
- JIRA JBehave : Issue Tracking

