Initial commit

Beginning code demonstrated in class.
Test for user signup form

This test will pass when a form can be submitted to sign up a new user
into the system.  It does not test all the functionality of the form
other than that it has a minimum of input and submission capability.
Add the user to the DB

This set of tests ensures that the User is added to the database when
submitting the new user form.  The tests include the fields that the
User needs to be able to save, but does not do error checking to
ensure that the fields are properly saved or validated.
Create tests for validating user.

These tests validate the user at the model and web submission levels.
They ensure that we will not accept an invalid user and require the
user to submit reasonable values for creating a new user.

The interface is not being tested, yet.  We do not ensure that when an
error occurs for these validations being triggered that we pass them
on to the user so that they can know what to do to correct the issue.
That will come later.
Test for user index and editing.

These tests are rudimentary tests to see if a user listing can be done
and whether a user can be edited after already in the system.  There
are loads of security flaws that could exist in an implementation that
are not addressed with these tests.  Those will come later after we
can be certain that users can log in to the system.
Tests for deleting users.

These simple tests just checks that the list of users includes links
to delete and that when clicked they are removed from the system.
Add tests for password field.

Do not allow password fields to be provided using text fields since
the text is visible on screen.
Add Bootstrap to Gemfile.
Simple tests for the Bootstrap navigation bar

This test simply checks that we've tried to put in a navigation bar
and the corresponding links.  It needs some fixing that will make it
more specific when a particular bug can be traced, but for now is
"good enough."
Fix within bug.

The within problem that was commented out now works properly with
proper refactoring.
Test login functionality.

With these tests, we ensure that the user must be logged in before
they can edit their profile and that the user is automatically logged
in when their account is created.
Update tests with administrator account

These tests now ensure that the proper privileges are observed when
creating/updating accounts so that only the right values can be
changed by the proper users in the usual and desired ways.  Most
functionality with the user login/logout/creation should be complete
at this point.
Clean up tests.

These commits simply make the tests way more readable and easy to
follow.  They should also make future tests easier to read and write
because they create new common functions that will occur frequently
throughout the rest of the upcoming tests.
Initial DB design

This commit reflects my first attempt at creating a DB that will work
for the rest of the project along with some very simple tests that
reflect that the DB is implemented properly.  It is expected that
discussion with students over the next several days will result in
modifications to the files since I might be missing a key feature that
they will notice and point out needs to be added to the system.
Initial DB design

This commit reflects my first attempt at creating a DB that will work
for the rest of the project along with some very simple tests that
reflect that the DB is implemented properly.  It is expected that
discussion with students over the next several days will result in
modifications to the files since I might be missing a key feature that
they will notice and point out needs to be added to the system.
Merge branch 'testing'

Conflicts:
	spec/models/contest_manager_spec.rb
	spec/models/contest_spec.rb
	spec/models/match_spec.rb
	spec/models/match_type_spec.rb
	spec/models/player_spec.rb
	spec/models/programming_language_spec.rb

Because I did a commit --amend to try to fix things and now I'm afraid
fast-forwarding will be permanently broken. :(  Hopefully, that isn't
the case, but we'll see.
1:N associations and create contest manager

These tests additionally check for one-to-many associations as well as
contain the initial tests for creating a contest manager.  The contest
manager tests will continue to need development.

As a part of this commit, we are creating code/ directories for
storing the contest managers, but .gitignore updates so those files
don't get included in the repo.  This should ensure that everyone has
the directories created for them, but doesn't try to pass around all
these managers accidentally.
Merge branch 'testing'
Test for final ERD layout

These tests ensure that the application meets the particular structure
laid out in the course-wide ERD.  By passing these tests, the models
should all have the correct attributes, but may be missing various
validations.  There are no functional tests correctly written, yet.
There are several ones started that are set to pending until they are
completed correctly.
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.