Created a pretty reporter

This is a simplified reporter from #283 
How important is a full stack trace while the tests are running? Too much information could scroll the test failure information off the screen. If I'm watching tests run and plan on being productive I mostly care about tests that produce errors first, then the line that caused the error, and the error name followed by the message. Everything else is mostly noise.