Boundary tests for arch
Adding basic test for User creation via API.

The following changes add a basic test for the creation of Users via the
API layer. More tests will be added in the near future.
Handling feedback from Jeremy.
Using ``orm.StringFiend`` for data-driven args.

Replacing the explicit use of ``FauxFactory`` by ``orm.StringField`` now
that we can specify the string type.
Updated User entity to use explicit string types.

Now that we can control what type of data is generated for
``orm.StringType``, I have updated the ``User`` entity to explicitly
require all string types provided by ``FauxFactory`` with the exception
of ``utf8`` strings for the ``login`` field, as they make ``Foreman`` to
barf and return a 500.
Fix ``orm.StringField`` usage and assertion.

Updated my call to ``orm.StringField`` to use the correct syntax as well
as perform the ``get_value()`` method inside the decorator. Also,
removed the ``password`` field from my assertion block since the ``GET``
method does not return it.
Merge pull request #1080 from omaciel/user-api-v2-test

Adding basic test for User creation via API.
Merge pull request #1076 from sghai/arch

Boundary tests for arch
convereted to data-driven tests
Merge pull request #1086 from sghai/data-driven

Converted arch tests to data-driven
Improve HTTP PUT API tests, reorganize code

There are API tests that issue HTTP PUT requests and check the status code
returned by those HTTP requests. However, there are not tests which check
whether the just-updated entities were correctly updated. Add tests of this kind.

Reorganize code. Move methods `test_post_and_get` and `test_put_and_get` into
their own test case. This is done so that the `longMessage` class variable can
be used. This variable allows good quality error messages to be written while
using a minimum of code.

Update the docstring for class `EntityTestCase`.

Add a new assertion to method `test_post_status_code` and update its docstring
accordingly.