Dan Graham 7ffda66813 Fixed W3C error messaging (#182)
* Do proxying for W3C responses
  * If a W3C Response is provided by a proxy, map to the correct error
  * Checks if `value` is an object and `value.error` and maps it based on that (`value.error` is the W3C error code)
  * Broke off `errorFromCode` into `errorFromMJSONWPStatusCode` and `errorFromW3CJsonCode`
* Rename '.error' property to correct W3C property
  * The error property in the ProtocolError objects should match up with https://www.w3.org/TR/webdriver/#handling-errors under the 'JSON Error Code' column
  * Added tests for all of these
* Make ProxyRequestError work for W3C
  * Added an arg called `.w3c` that passes in the proxied W3C error
  * Fixed the `getActualError` function that looks for the .w3c variable and parses error from the code
2018-02-05 11:55:56 -08:00
2018-02-05 11:55:56 -08:00
2017-11-17 10:01:16 -05:00
2018-02-05 11:55:56 -08:00
2016-07-12 09:48:01 -07:00
2017-08-30 15:46:57 -04:00
2018-02-05 11:55:56 -08:00
2016-10-26 14:19:14 -07:00
2018-02-01 08:38:13 -05:00

appium-base-driver

NPM version Downloads Dependency Status devDependency Status

Build Status Coverage Status

This is the parent class that all appium drivers inherit from, along with a collection of globally-used Appium driver utilities. Each utility is documented in its own README in the code:

Note: Issue tracking for this repo has been disabled. Please use the main Appium issue tracker instead.

Watch

gulp

Test

gulp once
S
Description
Cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol
Readme Apache-2.0
360 MiB
Languages
TypeScript 94%
JavaScript 5.1%
HTML 0.8%