-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[No QA] Add accessibility check to each PR in the deployChecklist #5117
[No QA] Add accessibility check to each PR in the deployChecklist #5117
Conversation
…klistAddAccessibleCheck
…klistAddAccessibleCheck
…klistAddAccessibleCheck
Un-JK, the fixes were easier than I was expecting (thank god) |
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.
Thanks for including lots of unit test updates. It's really important to give us more confidence about the live-testing. Another thing that might be useful is to just print the result of the generateStagingDeployCashBody
and paste it into a GitHub comment to get an idea what it looks like all rendered out. Only blocker is removing the accessibility stuff from the deploy blocker section.
Here's the example checklist from createOrUpdateStagingDeploy #5782 |
WTF I literally just removed that, that was the "thing I have to fix" because it wouldn't work in my test on this PR's description. I will add it back. 6e47e40 |
Updated, and updated the demo issue for the new format #5782 |
Looks good, but I'm not going to officially review as I contributed with the early commits. |
Holding this until we're sure applause is ready to start |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by @stitesExpensify in version: 1.1.8-10 🚀
|
🚀 Deployed to production by @roryabraham in version: 1.1.10-2 🚀
|
CC: @roryabraham
Details
We are adding accessibility to newDot! Because of that we need to update our deploy checklists to accommodate for both QA and accessibility testing.
Accessibility failures will not prevent deploys as of now because nobody is writing accessible code. In the future we will be including accessibility checkboxes as a deploy blocker.
Old Format:
Get started
button toFinish setup
when a user has draft data saved in the VBA flow #5258New Format:
Update
Get started
button toFinish setup
when a user has draft data saved in the VBA flow #5258[NoQA] Update "Troubleshooting" docs #5262
Fixed Issues
$ https://github.com/Expensify/Expensify/issues/175521
Tests
SO MANY automated tests, and that's about the best we can do unfortunately. This can't be tested locally.
QA Steps
Tested On
n/a
Screenshots
n/a