setup testling
switched out assertion library with should.js... I really should have written my own baby util library since that was the third time I've done that...
still working to get the tests running in ie... stupid IE
removed the console logger tests, as it previously fucked with the tape reporter
updated the rest-spec, and fixed an error in the integration tests after switching to expect
fixed a couple test that aimed at 0.8
removing IE from the browsers, because fuck IE
JSON.serialize was still stubbed when testling tries to phone-home about the test result
added angular to the scripts, which is sweet\!
added testling run to the travis build
merged master
after running the file logger tests, get rid of the test.log file.
updated es dep, includes the proper doc urls
added a check to the js_api generator that will ensure that each url has a unique variable signature.
merged lastest changes from master
changes to the testing, incorporating browser_testing
added browser tests, modified ci script, removed testing for version 0.90.x
fixed leaked vars in ci.sh
Merge remote-tracking branch 'upstream/master' into browser_tests_for_travis
Summary of Changes:
  - moved es install/start/stop logic into a seperate script
  - `grunt test` now runs the integration tests once for each version of ES we support
  - grunt can now install and run elasticearch (using grunt-run, pure js solution coming later)
  - included seperate es.sh script specifically for starting or stopping elasticsearch
  - url aliases, api, yaml_suite/index.js, and yaml_tests.json, are all now duplicated for 0_90 support
  - the client now accepts an apiVersion argument (undocumented) which defaults to 'master' but can be '0.90'
  - The yaml test runner will now check the name of the ES instance it is connecting to, preventing accidental wiping of ES