Test for user association from referees

We failed to check that all referees can refer to their creator.  This
test includes that association that wasn't being tested for
previously.  This existed in the ERD, but was simply missing in the
tests.
Initial Tests for creating Referees and Contests

These are the beginnings of tests that check that Referees and
Contests can be created.  More to come, obviously.
Delete contest_manager tests.

When synchronizing with implementation, I forgot to delete these
files.  This commit accomplishes that task.
Delete more tests

These are tests that are not implemented by students, but are
implemented by me. :(
Fill out referee tests.

These tests do a good job of completing the referee tests.  They are
quite robust now and try to check for most of the behavior that must
exist for the referee to be correct.  There should be quite a few less
tests for the referee after this commit, since the new tests would
have to deal with more edge cases and not the "normal" path through
the site.
Merge branch 'testing'
commit ignore
Merge tests
Merge branch 'master' of https://github.com/geisler/game_contest_server
Refine referee tests.

These are new tests to make the referee more robust.  Most of these
enhancements are based on watching various students implement the
referee incorrectly while passing all the existing tests.  These new
tests will make it harder for that to occur.
Create new tests for contest model

These tests are the beginning to ensure the contests are created
properly.  There are more functionality tests needed (e.g., ensure two
contests with the same name cannot be added), but the basics are in
place now.  This will provide a nice basis to ensure the contests are
written properly.
Initial routing tests.

These are starting to check that the proper routes have been defined.
The routes already should have been there, but this just
double-checks.  This could be more helpful down the road if we don't
define all the REST-ful routes, but depend on a subset.
More sophisticated validations of referee and contest

These tests make sure we are not putting bad values into the referee
or contest.  They are more complicated than the previous tests because
they consider the application logic and not just existence of data.
For example, the contest deadline must be in the future and the start
of the contest cannot start before the deadline.  There are several
other similar validations like this that just make sense when thinking
about the values that can be stored for these entities.
Fix illegal dates test.

There was a bug that had the illegal dates getting set up wrong, so
that start would be earlier than deadline and so it was possible to
find these dates as illegal via the wrong mechanism and still have an
error in them.  Fixed with this commit.
Use Timecop for making time work "properly"

By freezing time, we will be sure that the times we set for tests
doesn't advance before the tests against those same times execute.
Timecop simply makes sure that the time looks like it is fixed at some
point in time.  Now all references to now will return the same value
since time won't be advancing and things will "just work."

Possible Conflicts:
	Gemfile
	Gemfile.lock
Player model tests.

These tests check that the player model can properly keep track of all
the values that it is given.
Merge branch 'master' of https://github.com/geisler/game_contest_server

Conflicts:
	config/environments/test.rb
Initial player tests.

These are a very good start to getting player tests written and are
based largely on the tests for the other models.  I'm sure there will
need to be additional tests written as we find unique use cases for
this model that we haven't really tried to consider, yet.
Merging new tests
Merge branch 'master' of https://github.com/geisler/game_contest_server
Tests for matches.

These are a good set of tests for matches being displayed explicitly
and through the player views.  There will be more listed in the
matches views, but this is a very good start.
Final tests for course.

These are the final set of tests I was able to produce for the course.
There are likely other good tests to be had, but we've run out of
time.  Alas.  More tests will appear in the production version of the
code.