You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.
If the dom changes as the Chrome Accessibility Plugin generates its results then you can get StaleElementReferenceError without any context to tell you where this error came from.
I have spent the past 4 hours debugging this problem and finally have a working solution that at least gives you more useful information than the silent, context lacking failure that is currently returned.
If your tests fail because of StaleElementReferenceError then there is no context about where this is coming from.
By having the failure be handled inside of the plugin then grunt can fail gracefully.
Additionally, this provides context about where the error originated from.
Fixesangular#2331
If the dom changes as the Chrome Accessibility Plugin generates its results then you can get StaleElementReferenceError without any context to tell you where this error came from.
I have spent the past 4 hours debugging this problem and finally have a working solution that at least gives you more useful information than the silent, context lacking failure that is currently returned.
The failure that I was experiencing happened here: https://github.com/angular/protractor/blob/master/plugins/accessibility/index.js#L176
A better way to handle this would be to pass the error back into the failure reporter.
The text was updated successfully, but these errors were encountered: