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
Currently our test suite validates our PHP code. I propose that we create a front-end Systems Testing Suite that validates key components in the browser such as a11y, rendered markup, compiled assets, and any interactive components.
Using tools like Selenium WebDriver, HTML Codesniffers, and a testing framework like WordHat, we could further validate Beans in a virtual browser....automatically.
I'm starting a discovery phase to build a prototype systems tests suite.
The text was updated successfully, but these errors were encountered:
Rian Rietveld is also interested in this same test suite for the a11y team. We'll use ours as a study to develop the tooling and proof of concept. Then she'd like to use it as part of the automated a11y testing for core.
Her notes to me:
For my work I use aXe a lot. axe-core uses the Selenium’s WebDriver and now default uses the Chrome driver. aXe uses it’s own sniffers, especially developed for a11y testing.
Currently our test suite validates our PHP code. I propose that we create a front-end Systems Testing Suite that validates key components in the browser such as a11y, rendered markup, compiled assets, and any interactive components.
Using tools like Selenium WebDriver, HTML Codesniffers, and a testing framework like WordHat, we could further validate Beans in a virtual browser....automatically.
I'm starting a discovery phase to build a prototype systems tests suite.
The text was updated successfully, but these errors were encountered: