Bug 1328553 - Part 2: Add a netmonitor.requestsFinished timing to DAMP tests r?jryans MozReview-Commit-ID: 1v7yIUfEwan

Bug 1325277 - Re-enable leak checking for dom/animation/test/css-animations. r=ahal MozReview-Commit-ID: LSlEw5tCcTx

Bug 1326534 - Rename sessionCapabilities variable for brevity; r?whimboo MozReview-Commit-ID: KGYk2CgwERy

Bug 1326534 - Use session.Capabilities representation in listener; r?whimboo Capabilities are sent to the content frame script as a JSON blob. We can re-parse that in the listener to make use of the same complex object representation there. Because the listener is comprised of a set of top-level functions and not an object prototype, we cannot reuse the same pointer/getter trick as in testing/marionette/driver.js. However, we can change this later when we do introduce more robust code organisation to this file. MozReview-Commit-ID: 7PpholLqtF

Bug 1326534 - Reset session capabilities state on teardown; r?whimboo This change resets the session ID after all other state has been cleared, and also reinitialises `GeckoDriver#sessionCapabilities`, which was not done before. MozReview-Commit-ID: Jb40CXuX8h1

Bug 1326534 - Deploy WebDriver conforming capabilities in Marionette; r?automatedtester,whimboo,maja_zf This change removes session capability processing from testing/marionette/driver.js and replaces it with testing/marionette/session.js and `session.Capabilities`. Session timeout durations used to be stored in properties exposed directly on the `GeckoDriver` prototype, but these are now represented by `GeckoDriver#timeouts`, which is a pointer (getter) of `GeckoDriver#sessionCapabilities#timeouts`. The same is true for other session-scoped state. Since capabilities parsing is not unique to starting a new session, the errors thrown by `session.Capabilities.fromJSON` are re-thrown in `GeckoDriver#newSession` since it is required that we return a `SessionNotCreatedError` on parsing them during session creation. MozReview-Commit-ID: I3Xu2v71n4S

Bug 1326534 - Rewrite capabilities parsing in Marionette; r?automatedtester This patch provides a (nearly) WebDriver conforming implementation of capabilities in Marionette. The work remaining is pending further clarification in the specification. Capabilities are represented internally as a complex object provided by `session.Capabilities`. Timeouts and proxy configuration are also represented by the similar complex objects `session.Timeouts` and `session.Proxy`, respectively. The capabilities stored in `GeckoDriver#sessionCapabilities` are the result of parsing user-provided desired- and required capabilities. WebDriver now uses `firstMatch` and `alwaysMatch` primitives for capabilities, but as this is considered a wider breaking change, the move to these primitives will be done at a later stage. It’s prudent to point out that the base techniques used with the new primitives are similar to those implemented for `desiredCapabilities` and `requiredCapabilities` in this patch, and that the work needed to adapt them is considered trivial. When capabilities are presented back to the user (the so called processed capabilities), we call the `toJSON` implementation on the complex objects. `session.Capabilities#toJSON` calls the internal function `marshal` which ensures empty fields are dropped. `marshal` can be considered to be a specialisation of the standard library `JSON.stringify`, which also calls `toJSON` on entry values if they provide this function. The changeset overall also provides a much deeper level of testing of WebDriver capabilities. MozReview-Commit-ID: 97xGt3cnMys

Bug 1326534 - Correct capability wrapping in tests; r?automatedtester Capabilities should be sent in either a `desiredCapabilities` or a `requiredCapabilities` block inside `capabilities`: {capabilities: {requiredCapabilities: {acceptInsecureCerts: true}}} Marionette currently accepts capabilities in the top-level dictionary, but this is not conforming to the WebDriver. MozReview-Commit-ID: 9JWjvPKBp6S

Bug 1326534 - Propagate stacktraces for WebDriver errors; r?automatedtester When we currently create new WebDriver errors we throw away the stacktrace generated by `WebDriverError`'s prototype, `Error`. This change stores the stacktrace, which will cause it to be serialised and returned to the client. This change is not as valuable as storing the stacktraces of internal errors, but brings symmetry to our error handling and may be useful if only to navigate to the source of an error. MozReview-Commit-ID: LCFMwKxxcTp

Bug 1326534 - Lint a few statements in driver.js; r?automatedtester No functional changes. MozReview-Commit-ID: FP9p9tPr8Ce

Bug 1326534 - Add assert.in for own properties; r?automatedtester The implementation of the new library function `assert.in` is analogous to Python's `unittest.TestCase.assertIn`. MozReview-Commit-ID: 1pjS9ttPXgo

Bug 1326534 - Add test for assert.array; r?automatedtester MozReview-Commit-ID: IWUnhCgPp1R

Bug 1326534 - Preserve stacks when passing error protos to WebDriverError; r?automatedtester The `stack` argument to `WebDriverError` has never been in use. Following the API of the `Error` prototype, this changes its constructor to take one argument which can either be a string of an `Error`. When internal errors are thrown in Marionette, they are usually wrapped in `WebDriverError` but we currently lose track of its stack. This preserves the wrapped error's stacktrace by setting the `stack` property. Practice have found that they are very useful to return to the client, as they are currently only printed to stdout. MozReview-Commit-ID: 9sTdP4TntIc

Bug 1326534 - Exclude array and null from being counted as objects; r?automatedtester Calling `typeof` on arrays or null in JavaScript returns `"object"`, and a safer check is to rely on `Object.prototype.toString`. MozReview-Commit-ID: 5VxXf2ByoEx

Bug 1326534 - Correct tests for mandated and supported capabilities; r?automatedtester MozReview-Commit-ID: 932AoNlBtwt

Bug 1328553 - Signed DAMP changes MozReview-Commit-ID: LADBIPiXlse

Bug 1294541 - Merged changesets. r?dao MozReview-Commit-ID: 7V2Wvb2TPe3

Bug 1286948 - onEnterFrame/onLeaveFrame wasm events and callstack. r?shu Handles onEnterFrame and onLeaveFrame trap handling. The FrameIter is used in the DebuggerFrame instead of ScriptFrameIter. The debug wasm frame is created and can be found on callstack during those event. MozReview-Commit-ID: 8oyFkrINc0A

Bug 1286948 - Adds prolog and epilog debug traps and handlers. r?luke Using toggled call/traps to invoke handler to process enter and leave frame events. MozReview-Commit-ID: APTt3N6Zt0P

Bug 1286948 - Extends AbstractFramePtr to reference wasm::DebugFrame. r?shu, luke Debugger.cpp use FrameIter to walk the stack. Having extended AbstractFramePtr helps with simulating wasm callstack as JS one. MozReview-Commit-ID: 7zGWZp33sme