Commit Graph

12 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
eae5758ff4 Split template tests into logic groups, test for template without
tokens.
2013-02-15 17:38:11 -05:00
Vladimir Agafonkin
ed8dc9f4cd improve core specs #1347 2013-02-04 18:31:14 +02:00
snkashis
6b4f5c4cf7 handling no existingUrl scenario 2012-12-27 14:39:19 -05:00
snkashis
3d416f38e1 whitespace for hash 2012-12-26 11:45:38 -05:00
Steve
3208db476c Semicolons in spec 2012-12-22 23:52:25 -05:00
snkashis
8c7c06431a handle existing query strings for WMS urls , #973 2012-12-22 17:47:38 -05:00
Vladimir Agafonkin
382ef5c0b2 spec cleanup 2012-07-05 12:54:40 +03:00
mourner
42bcb9b3b3 DomUtil, DomEvent, namespace config improvements, some specs 2010-09-07 14:27:44 +03:00
mourner
4854e0f9f7 minor renaming 2010-09-06 19:14:04 +03:00
mourner
0eb9cd8cc6 L.Util.stamp & specs 2010-09-06 16:17:06 +03:00
mourner
341f6e726f added Events, folder renaming 2010-09-03 17:38:41 +03:00