-
Notifications
You must be signed in to change notification settings - Fork 2.3k
feat(a11yPlugin): add support for Tenon.io #1867
Conversation
86f1913
to
14608c3
Compare
One thing we will need to document: in Tenon, scripts have to be accessible from the page source as a string, for example loaded through a CDN. Otherwise Tenon won't be able to test expressions coming from Angular. I ran into this when supplying an alt attribute as an expression. To get around it for now, I just hard-coded a value. |
* printAll: false, // whether the plugin should log API response | ||
* }, | ||
* chromeA11YDevTools: false, | ||
* path: 'node_modules/protractor.plugins/accessiblity' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: .plugins instead of /plugins
Looks good overall, just a couple comments. |
14608c3
to
ea0f72d
Compare
@juliemr FYI I pushed all changes except for the duration thing, which I figured could come later. Let me know if there's anything else you'd like to see updated. |
Looks good. Merged as 13d34c9 |
Woooot! 🎉 @karlgroves Tenon is merged into Protractor master! |
👍 |
w00t! |
As part of #1854, this change adds support for the Tenon accessibility testing framework. I removed my API key from the plugin config files, so the Protractor internal tests won't run against Tenon as-is. The Chrome Accessibility Dev Tools will still run, though.
One thing I noticed was that the
accessibility-developer-tools
package was missing from package.json. I added it back in along with theentities
package for decoding HTML strings, which has no dependencies.