### Home Classes Methods

### Files

- CONTRIBUTION_GUIDELINES.rdoc
- README.rdoc

### Class Index

Quicksearch

- Shoulda
- Shoulda::ActionController
- Shoulda::ActionController::Macros
- Shoulda::ActionController::Matchers
- Shoulda::ActionMailer
- Shoulda::ActionMailer::Assertions
- Shoulda::ActionMailer::Matchers
- Shoulda::ActiveRecord
- Shoulda::ActiveRecord::Assertions
- Shoulda::ActiveRecord::Helpers
- Shoulda::ActiveRecord::Macros
- Shoulda::ActiveRecord::Matchers
- Shoulda::Assertions
- Shoulda::ClassMethods
- Shoulda::Helpers
- Shoulda::InstanceMethods
- Shoulda::Macros
- ActionController
- Test

No matching classes.

We’re using GitHub, and we’ve been getting any combination of github pull requests, tickets, patches, emails, etc. We need to normalize this workflow to make sure we don’t miss any fixes.

- Make sure you’re accessing the source from the official repository.

- We prefer git branches over patches, but we can take either.

- If you’re using git, please make a branch for each separate contribution. We can cherry pick your commits, but pulling from a branch is easier.

- If you’re submitting patches, please cut each fix or feature into a separate patch.

- There should be an issue for any submission. If you’ve found a bug and want to fix it, open a new ticket at the same time.

- Please don’t send pull requests Just update the issue with the url for your fix (or attach the patch) when it’s ready. The github pull requests pretty much get dropped on the floor until someone with commit rights notices them in the mailbox.

- Contributions without tests won’t be accepted. The file `/test/README` explains the testing system pretty thoroughly.

[Validate]

Generated with the Darkfish Rdoc Generator 2.