100% Test Coverage

[BenjamenMeyer]

A significant portion of the functionality it tested; however, it's not 100% tested nor 100% proven.
This will be resolved when:

• every class can be shown to be tested via its own test module
• every method in a module and class can be shown to be tested
• every branch within a method can be shown to be tested

Validation of this will be done by running each individual test on its own and proving that the code it's testing is 100% covered, f.e tox -e py27 -- stackinabox/tests/test_httpretty.py shows stackinabox.util.httpretty as being 100% covered.

Additional points to note:

• it may be good to refactor the util modules to break them down more; example is the stackinabox.util.requests_mock.core module which could probably be about 3 or 4 modules on its own.
• refactor the tests to break down more explicitly what is going on and use subdirs that match up to their original branches to as well, thus stackinabox.util.httpretty would map to stackinabox.tests.util.httpretty for any tests covering classes and methods of the httpretty utility.