(#410) Move acceptance style spec tests into the acceptance directory

The previous "spec" test suite was really an acceptance / integration level
test: you had to have a fully functional end to end Razor stack to run
the test - including the nodejs web components, a data store, etc.

This is really valuable, and has brought a lot of value to development, but it
also makes it very hard to add actual unit style tests to validate small parts
of the functionality of the Razor codebase.

This moves aside the acceptance spec files, so that we no longer have them
sitting where Ruby convention dictates a unit style test suite would live.

Signed-off-by: Daniel Pittman <daniel@rimspace.net>
Remove the local .rspec options file

The Razor repository includes an rspec options file, setting some cosmetic
options.  This will override any user configuration in their `~/.rspec` file,
which means that every developer is forced to use the same cosmetic output.

That really isn't polite - we should respect individual decisions about
unimportant aspects like the spec output format; removing this file allows
for that.

The worst case is that someone who expected the old behaviour now sees
the (admittedly, terrible) rspec default output format until they create their
own personal configuration in their home directory to fix that.

(Of course, they will then benefit: every project they work in will have those
defaults they like applied, so it should be an overall quality of life win
for everyone. :)

Signed-off-by: Daniel Pittman <daniel@rimspace.net>
(#410) Build the stub rspec unit test suite

This adds the bones of an rspec test suite.  While *cough* extremely
limited *cough* at the moment, having the framework in place makes it easier
to start adding flesh to these empty bones.

Signed-off-by: Daniel Pittman <daniel@rimspace.net>
(#410) Create template spec stubs for all conventional classes

This creates a stub template spec with a minimal test - can the code load, and
does it define the constant we expect - for everything that complies with Ruby
convention for how code is loaded.

These are not deep tests, but they should ensure that we, at the least, manage
to load most of the code in the project when we run the spec tests.  That will
catch the worst of errors, that we fail to require the right things, or that
we have a syntax error.

Signed-off-by: Daniel Pittman <daniel@rimspace.net>
Update test documentation to reflect unit test creation

This updates the testing guide to point folks at the unit tests, and to
indicate how to run the acceptance suite.

Signed-off-by: Daniel Pittman <daniel@rimspace.net>
Merge pull request #411 from daniel-pittman/feature/master/410-make-a-real-unit-test-suite-for-razor

#410 make a real unit test suite for razor