Complete test review

[AdamSLevy]

A complete review of the existing tests should be done to ensure:

• Appropriate levels of test coverage for all areas of the code. Note that this does not by any means specify a specific % level of coverage. In fact 100% is too much. The package is coded defensively, which means a lot of code paths are difficult to reach. Don't bend over backward to get coverage through every if err != nil { branch when that error is very unlikely.
• Clarity of tests
• Consistency and reduction of runtime dependencies.
• Integration and Unit test distinction. Many of the tests actually query factomd, making them an integration test. So allow test control with use of flags (if a test needs to hit an API, allow that to be skipped).