Commit Graph

5 Commits

Author SHA1 Message Date
John Firebaugh
01332ebead Omit "should" in spec descriptions
The rationale is this: the spec string describes the expected
behavior unconditionally. The code examples, on the other hand,
set up an expectation that is tested with the call to the expect
method. The code examples can violate the expectation, but the
spec string does not. The value of the spec string is as clearly
as possible describing the behavior. Including “should” in that
description adds no value. (From http://rubyspec.org/style_guide/)
2013-02-19 12:41:48 -08:00
Tom MacWright
0a2000166a Fix semicolons, breaking, whitespace, duplicate var statements. 2013-02-19 11:18:15 -05:00
Mourner
76d517e3e2 temporarily disable projection specs (need rewrite after refactoring) 2011-07-12 15:32:22 +03:00
mourner
16097461f5 Projection fixes, specs 2010-09-07 11:59:58 +03:00
mourner
f734679158 Projection without specs 2010-09-06 19:17:27 +03:00