Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Systems Testing Suite #236

Open
hellofromtonya opened this issue May 22, 2018 · 1 comment
Open

Systems Testing Suite #236

hellofromtonya opened this issue May 22, 2018 · 1 comment

Comments

@hellofromtonya
Copy link
Contributor

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.

@hellofromtonya
Copy link
Contributor Author

hellofromtonya commented May 22, 2018

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.

@hellofromtonya hellofromtonya added this to the v2.0 milestone Jul 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
v2 Roadmap
  
Planning and Organization
Development

No branches or pull requests

2 participants