add guard for automated test running
make some tests fail
colorize test output
write some tests, make them pass
ensure known operands aren't clobbered by number generator
get rid of silly test
reformat test
rm redundancy (naming changes, extract method)
bump rspec version to test something
rm comments, modify constant
use Array#concat instead of push + flatten
rm unused method
:facepunch: get the numbers crunching without using classes

having a problem with division not being calculated with sufficient
precision unless decimails are used for at least one of the significant
operands
get problem generation working with url params
allow at least one known operand in url

URL FORMAT: <host>/problem/subtraction/hard/50
there is something strange going on with the parameter collection and
the type coercion. Operands are expected as an array, but params returns
strings. Need to go through and change all operands to numbers and fit
them in an array. This is probably happening at the wrong place in the
application
rm stale examples
rename method
update routes for better granularity
exponents aren't primes. :grimacing:
Merge pull request #2 from evanbleiweiss/testing-one-two

Rework class based approach for problem type evaluation