Allow Raptor tests to be run with --enable-accessibility
Categories
(Core :: Disability Access APIs, task)
Tracking
()
People
(Reporter: morgan, Assigned: morgan)
References
(Blocks 2 open bugs)
Details
The Raptor harness does not currently support a11y instantiation or awaiting/responding to a11y events. We can instrument the harness to manage this, similar to the way addAccessibleTask functions for our browser tests. We'll also need to add some kind of "checkBeforeFinishing" function to ensure all events and cache pushes relevant to the test have made it to the parent process. We do this in our existing performance tests by awaiting a final EVENT_SHOW or REORDER. The thing we await is test-specific, and I'm not sure we've got an easy way to generalise at this juncture, but maybe we can create a standard function in the harness which can be awaited.
Raptor tests don't currently support the use of SpecialPowers, so we're limited to poking things in parent.
| Assignee | ||
Updated•1 month ago
|
Updated•1 month ago
|
Description
•