-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Add automated a11y tests #23057
Add automated a11y tests #23057
Conversation
# Conflicts: # firefox-ios/firefox-ios-tests/Tests/XCUITests/FakespotTests.swift
Client.app: Coverage: 30.16
ComponentLibrary: Coverage: 30.84
Generated by 🚫 Danger Swift against d9f160d |
@@ -321,4 +321,42 @@ class OnboardingTests: BaseTestCase { | |||
let topSites = app.collectionViews.cells[AccessibilityIdentifiers.FirefoxHomepage.TopSites.itemCell] | |||
mozWaitForElementToExist(topSites) | |||
} | |||
|
|||
func testFirstRunTourAccessibility() throws { |
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.
@isabelrios Should we put such a test in TestRail and insert the TestRail link here?
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.
This test looks very similar to this one:
func testFirstRunTour() { |
@thatswinnie are we missing something there? We can add it there so that we don't duplicate the complete test... Thanks!
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.
Oh never mind, just saw the call to try app.performAccessibilityAudit()
we could add that in the exisiting test though...
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.
Discussed offline. We agreed to have this test as part of the exisiting UI testFirstRunTour
. Then, the MTE team will create a specific test plan for a11y tests that can run as another workflow in parallel with the existing Smoketests and move this and other tests that will be implemented to it.
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.
FYi ^ @mdotb-moz
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.
Awesome!! 👏
📜 Tickets
Jira ticketGithub issue💡 Description
This adds automated a11y audits to onboarding, tab tray and overlay mode. It fixes three issues found while running the tests.
📝 Checklist
You have to check all boxes before merging
@Mergifyio backport release/v120
)