Fixed issue #13

Created a TestObjectFactory to return a "TestableAppConfigurator." As the name infers, this feels like a step towards a TestableAppConfigurator class using the testable pattern.

http://www.mattwrock.com/post/2011/12/07/Unit-Testing-ASPNet-Http-Handlers-and-a-discussion-of-Auto-Mocking-and-the-Testable-pattern.aspx

Another route might be to make the AppConfigurator class itself (or configuration generally) more testable and I would be interested if anybody has any thoughts on how that might be improved.

I made the AppConfigurator support more of a traditional builder pattern as well as the action based configuration it already has. I don't know if this increases flexibility or confusion?