Commit Graph

12 Commits

Author SHA1 Message Date
Nathan Cahill
1eafc015c1 create points from objects with x and y properties (#4465) 2016-04-20 17:05:31 +02:00
Vladimir Agafonkin
cfdbd10431 enforce indentation in specs 2015-09-25 13:55:37 +03:00
Vladimir Agafonkin
91c039b7aa jshinting and major clean up of specs code, ref #2151 2013-11-07 23:54:33 +02:00
Tom MacWright
a2f7d7e834 Use mocha 2013-04-03 14:50:09 -07:00
Vladimir Agafonkin
9c2e7cfbd4 add Point contains method 2013-02-22 17:28:55 +02:00
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
17cf297c9b complete geometry tests to 100% #1347 2013-02-05 13:51:27 +02:00
mourner
a2d2fed2db new Point methods 2010-09-17 19:04:41 +03:00
mourner
06d043853d multiplyBy 2010-09-15 16:45:02 +03:00
mourner
59a1736b3e Point fixes 2010-09-13 14:58:03 +03:00
mourner
a8d55d0d47 Point add/subtract/divideBy 2010-09-10 16:54:03 +03:00
mourner
7a1dcd9915 Transformation & Point classes, more specs 2010-09-02 18:23:53 +03:00