Closed Bug 1201595 Opened 4 years ago Closed 4 years ago
Improve overall stability of a11y checks in Marionette
40 bytes, text/x-review-board-request
Right now it's not easy to figure out where the accessibility failure happened without a stacktrace and walking through the test code. We need to return the information about the location of the error in addition to the type of the problem.
* Improve error messaging for accessibility related failures in Marionette. * Check accessibility after non-accessibility related checks on user actions (so if there's a non a11y related failure it happens fist) * Improve overall stability of a11y checks
Summary: Improve error messaging for accessibility related failures in Marionette. → Improve overall stability of a11y checks in Marionette
Bug 1201595 - improving a11y checks reliability and error messaging. --- .../marionette/tests/unit/test_accessibility.py | 4 +- testing/marionette/driver.js | 2 +- testing/marionette/elements.js | 9 ++- testing/marionette/listener.js | 85 +++++++++++----------- 4 files changed, 53 insertions(+), 47 deletions(-)
Attachment #8659368 - Flags: review?(ato)
Comment on attachment 8659368 [details] MozReview Request: Bug 1201595 - improving a11y checks reliability and error messaging. https://reviewboard.mozilla.org/r/18805/#review16817
Attachment #8659368 - Flags: review?(ato) → review+
woops this is the right try run: https://treeherder.mozilla.org/#/jobs?repo=try&revision=1ead43822811 (cancelled old one)
You need to log in before you can comment on or make changes to this bug.