-
Notifications
You must be signed in to change notification settings - Fork 153
DataMapper 0.10.0 (Next Branch)
The purpose of this branch is fix DataMapper’s broken specs.
The goal is to spec only DataMapper’s public and semi-public API and achieve full spec coverage of all DataMapper code, without using any mocks.
Note: It is acceptable, and almost certainly probable, that the spec suite will have many failures while this project is ongoing. I have removed any requirement to have DO installed to run the specs, and set it up to use the in-memory adapter as the default spec adapter.
Must Read: Spec Writing Guide
The DataMapper API has been divided up into three categories: public, semi-public and private. Public includes anything that the end user interacts with. Semi-public is hidden from public view, and is provided primarily for plugins.
Anything that is NOT a public or plugin API should not be specced. All the functionality of private methods should be specced through the private API.
All public and semi-public API code must include specs, while private API code must never be specced directly.
All public and semi-public API code should be documented using the YARD documentation format prior to writing it’s specs.
Using mocks within the specs will result in instance revocation of your commit access. No exceptions.