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.
Merged with Dr. Geisler's repo