Previously it was difficult to know which SPEC failed, because of the timeout.
Previously the value of 300 seconds was hard coded.
Attempting to support a noConflict option similar to jQuery's noConflict. If Evergreen nukes a pre-existing method like `require`, calling `Evergreen.noConflict()` will retrive the old definition, and the developer is required to use `Evergreen.require` instead of `require` The code is pretty crude, but any sort of refactor seems to upset poltergeist, so I'll get to refactoring this later This should satisfy issue #17.
With the many troubles we've had compiling the capybara-webkit gem, I thought it best to remove it, as it is not necessary for this gem to be devloped/used. We've also seen some performance improvement on headless environments using phantomjs with poltergeist on apps using evergreen.