Dan Graham a74d25cb1e Fix: Throw error after parsing protocol from proxied response (#211) ...

* Before it was throwing immediately which meant we weren't parsing the protocol and weren't showing the proper error responses
* If proxied W3C error doesn't have an error, make it `Unknown Error`

2018-05-14 08:36:49 -07:00

..

.jshintrc

Rename 'mjsonwp' to 'protocol' (#178)

2018-01-29 12:41:14 -08:00

errors-specs.js

Sync w3c codes with the recent spec (#193)

2018-03-05 19:19:45 +01:00

fake-driver.js

Rename 'mjsonwp' to 'protocol' (#178)

2018-01-29 12:41:14 -08:00

helpers.js

Rename 'mjsonwp' to 'protocol' (#178)

2018-01-29 12:41:14 -08:00

protocol-e2e-specs.js

Fix: Throw error after parsing protocol from proxied response (#211)

2018-05-14 08:36:49 -07:00

protocol-specs.js

Fix: Throw error after parsing protocol from proxied response (#211)

2018-05-14 08:36:49 -07:00

routes-specs.js

Add an optional flags parameter to press_key_code endpoint (#208)

2018-05-07 18:29:21 +02:00

validator-specs.js

Rename 'mjsonwp' to 'protocol' (#178)

2018-01-29 12:41:14 -08:00