alternative way to export/import globals(thats quick and easy, while tdd'ing)
cleanup, playing with conventions, clarity
explicitly define globals on a globals object

conventions - if they're globals, lets explicitly make that
crystal clear by defining them on an object named as such.

For now, keep implicit importing of the globals object which keeps the
usage of such global methods in the tests implicit as well,
but makes for easier refacotring later if this is the wrong
stategy + it keeps the tests less cluttered
third way of dealing with globals

this approach however does not declare a 'globals' variable in the
global scope, which is one step better. It does still define all the
methods on window though
use root instead of globals; assign to global(for node) or window if global does not exist
whereby I realize that modules already are wrapped; don't wrap in anonymous function something that will be wrapped in a module enclosure
fix issue with random timer
messing with time, event loops, etc
fixed indeterminate tests
organize; warmup
long note about indeterminate tests from last night
fully fixed indeterminate tests in the tests themselves, not in the implementation
install mocha side by side with qunit to compare/contrast the two
add mocha tests for wantPromise