cschabetsberger-micro-focus b7b0b7b2f3 Detect a non-working chromedriver connection after androidDriver.closeApp() and androidDriver.launchApp() (#136) ...

* * Make sure to detect a non-working chromedriver connection after calling androidDriver.closeApp() and androidDriver.launchApp() by returning the result body (resBody) only if it does not contain a status code

* Adapted unit test to cover the case when chromedriver responds with http
200 but status code != 0 (which represents an error)
Also fixed a typo in another test description

2017-10-13 09:05:02 -04:00

..

mock-request.js

copy over initial jsonwp-proxy files

2016-05-06 08:42:28 -07:00

proxy-e2e-specs.js

code updates for jwproxy merge

2016-05-06 08:42:28 -07:00

proxy-specs.js

Detect a non-working chromedriver connection after androidDriver.closeApp() and androidDriver.launchApp() (#136)

2017-10-13 09:05:02 -04:00

url-specs.js

code updates for jwproxy merge

2016-05-06 08:42:28 -07:00