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
..
jasmine	update Jasmine to 1.3.1	2013-01-31 14:31:53 +02:00
suites	Omit "should" in spec descriptions	2013-02-19 12:41:48 -08:00
after.js	cleanup testacular config	2013-01-31 15:44:55 +02:00
before.js	cleanup testacular config	2013-01-31 15:44:55 +02:00
happen.js	Add a baselayerchange event	2012-10-12 12:19:21 -07:00
runner.html	fix browser test runner, close #1418	2013-02-19 18:21:01 +02:00
testacular.conf.js	make test task less verbose	2013-02-04 14:30:49 +02:00