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
Vladimir Agafonkin
f01e32d764 fix specs sometimes failing 2013-02-05 17:00:38 +02:00
danzel
61ce465134 Fix up the unit tests. Polyline.closestLayerPoint and noConflict were broken. 2012-06-25 12:16:46 +12:00
mourner
ff36820cf9 fix namespace spec 2010-09-23 17:25:55 +03:00
mourner
42bcb9b3b3 DomUtil, DomEvent, namespace config improvements, some specs 2010-09-07 14:27:44 +03:00