blocking-proxy

Blocking Proxy

TODO

• API commands
• Set stability function and args
• simplify running e2e tests
• set up travis
• Timeout behavior
• proper propagation of errors
• Logging level or log to file

Protractor needs to be able to start this in a separate process - it should work with all the existing methods of starting up webdriver.

Should pass up errors in a reasonable way.

Running e2e tests

Start webdriver

webdriver-manager update
webdriver-manager start

in another terminal, start the testapp

npm run testapp 

Start the proxy with

npm start

in yet another terminal, run the tests

npm run test:e2e

Changelog

0.0.4

• (8f8b8b3) tests(context): test that the this variable points to the right thing

  Note: this means that using this.addMatchers no longer works inside before blocks or specs. It should have been changed to jamsine.addMatchers since the upgrade to Jasmine 2. It was still working by accident up until the previous commit.

• (c0f13d2) refactor(asyncTestFn): refactor async test wrapping to show more info

  Test wrapping for Jasmine 2 now more closely follows the test wrapping for Mocha at https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/testing/index.js

  This also adds more information to the task names in the control flow, for easier debugging.