Conversation
|
PR is blocked until the aria-practices removes husky from its postinstall script. I opened a PR for that: w3c/aria-practices#2033 |
| jobs: | ||
| - dependencies_unix | ||
| - test_nightly: | ||
| - test_nightly_chrome: |
There was a problem hiding this comment.
How will we know if/when this fails? Is there someone responsible for checking CI logs daily?
There was a problem hiding this comment.
Yeah, those get kicked out to our #attest-build channel on Slack.
There was a problem hiding this comment.
I also get emails every night about the run and see if they pass/fail
61891e9 to
300e0d1
Compare
| unix_box: &unix_box | ||
| docker: | ||
| - image: circleci/node:10-browsers | ||
| - image: circleci/node:16-browsers |
There was a problem hiding this comment.
So that we get access to Chrome 95
There was a problem hiding this comment.
Just an fyi, circle is changing how they tag their images (should be cimg/node:16.13-browsers https://circleci.com/developer/images/image/cimg/node). I'll update the tag in another pr because we can also specify using lts-browsers which I think would be good to test on our nightly builds
| unix_box: &unix_box | ||
| docker: | ||
| - image: circleci/node:10-browsers | ||
| - image: circleci/node:16-browsers |
There was a problem hiding this comment.
Just an fyi, circle is changing how they tag their images (should be cimg/node:16.13-browsers https://circleci.com/developer/images/image/cimg/node). I'll update the tag in another pr because we can also specify using lts-browsers which I think would be good to test on our nightly builds
| jobs: | ||
| - dependencies_unix | ||
| - test_nightly: | ||
| - test_nightly_chrome: |
There was a problem hiding this comment.
I also get emails every night about the run and see if they pass/fail
| "fmt": "prettier --write .*.json *.{json,md,js} **/*.ts './{.circleci,.github,build,doc,lib,locales,test,typings}/**/*.{json,md,js,ts,html}'" | ||
| }, | ||
| "devDependencies": { | ||
| "@axe-core/webdriverjs": "^4.2.2", |
There was a problem hiding this comment.
This is a circular dependency, will this cause any problems (probably not, but want to make absolutely sure)?
There was a problem hiding this comment.
Don't think so. It's a dev dependency.
| "@babel/preset-env": "^7.5.4", | ||
| "@deque/dot": "^1.1.5", | ||
| "act-rules.github.io": "github:act-rules/act-rules.github.io#master", | ||
| "aria-practices": "github:w3c/aria-practices#f7de7ec3a53534018237f24cb9e610f26c30c367", |
There was a problem hiding this comment.
How often should we update the commit hash?
There was a problem hiding this comment.
I was thinking that if nightly fails, we take another look. Don't think we need to do it more often than that.
| const port = 9515; | ||
| let driver, server, addr, axeSource; | ||
| this.timeout(50000); | ||
| this.retries(3); |
There was a problem hiding this comment.
Was this failing a lot that it needed retries?
There was a problem hiding this comment.
I'm not entirely sure. I did see it failing once or twice for a reason I couldn't figure out. Don't know for sure what the reason of that was. Don't think having this here hurts.
| 'region', // dequelabs/axe-core#3260 | ||
| 'heading-order', // APG issues | ||
| 'list', // APG issues | ||
| 'scrollable-region-focusable', // w3c/aria-practices#2114 |
There was a problem hiding this comment.
I like these comments a lot. Thanks for adding them.
test/aria-practices/apg.spec.js
Outdated
| await new Promise(r => setTimeout(r, 500)); | ||
| await connectToChromeDriver(port); | ||
|
|
||
| const app = express(); |
There was a problem hiding this comment.
Are any of the test files using absolute paths? If not I think our npm run start command should serve node_modules directly as well, so we might not need express for this.
There was a problem hiding this comment.
Fair point, let me see if I can make that work.
Co-authored-by: Steven Lambert <2433219+straker@users.noreply.github.com>
| "@babel/preset-env": "^7.5.4", | ||
| "@deque/dot": "^1.1.5", | ||
| "act-rules.github.io": "github:act-rules/act-rules.github.io#master", | ||
| "aria-practices": "github:w3c/aria-practices#f7de7ec3a53534018237f24cb9e610f26c30c367", |
There was a problem hiding this comment.
I was thinking that if nightly fails, we take another look. Don't think we need to do it more often than that.
| const port = 9515; | ||
| let driver, server, addr, axeSource; | ||
| this.timeout(50000); | ||
| this.retries(3); |
There was a problem hiding this comment.
I'm not entirely sure. I did see it failing once or twice for a reason I couldn't figure out. Don't know for sure what the reason of that was. Don't think having this here hurts.
test/aria-practices/apg.spec.js
Outdated
| await new Promise(r => setTimeout(r, 500)); | ||
| await connectToChromeDriver(port); | ||
|
|
||
| const app = express(); |
There was a problem hiding this comment.
Fair point, let me see if I can make that work.
| npm run test -- --browsers Chrome,FirefoxNightly | ||
|
|
||
| # Run the test suite for nightly builds. | ||
| test_nightly_aria_practices: |
There was a problem hiding this comment.
We should do this same nightly thing with ACT rules. I'll open that PR when this is merged.
One of the more common reasons for reported false positives comes from axe-core failing something recommended in the ARIA practices. This PR adds a test script will have axe-core running against the ARIA practices.
Closes issue: #2918