-
Notifications
You must be signed in to change notification settings - Fork 698
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 AXE testing to test suite #3764
Add AXE testing to test suite #3764
Conversation
<!-- These ALL fail our axe scanning so we comment them out. --> | ||
<!-- | ||
<muxc:NumberBox Header="Sample NumberBox"/> | ||
<muxc:NumberBox AutomationProperties.Name="Sample NumberBox"/> | ||
<muxc:NumberBox Header="Sample NumberBox" SpinButtonPlacementMode="Inline"/> | ||
<muxc:NumberBox Header="Sample NumberBox" SpinButtonPlacementMode="Compact"/> | ||
--> |
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.
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.
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 right, forgot about that issue. I'll remove the code then.
@@ -39,7 +39,8 @@ | |||
<StackPanel Orientation="Horizontal"> | |||
<Button x:Name="BackButton" Margin="0,0,4,0" | |||
Style="{ThemeResource AccentButtonStyle}" | |||
AutomationProperties.AutomationId="__BackButton" | |||
AutomationProperties.AutomationId="__BackButton" | |||
AutomationProperties.Name="Back" |
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.
Needed to add that since otherwise, Axe would always return at least one a11y issue.
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@StephenLPeters CI failed since the required NuGet packages are not available in the WinUI dependency repository. |
@kmahone Can you remind us the process of getting the nuget package into the dependencies? |
nuget push mypackage.nupkg -Source https://pkgs.dev.azure.com/ms/microsoft-ui-xaml/_packaging/MUX-Dependencies/nuget/v3/index.json -ApiKey az |
@StephenLPeters @ranjeshj Is there anything on my side that needs to be changed for this PR? |
@chingucoding Apologies on the delay. Can you sync with master ? There have been quite a few changes since this PR. |
Merged with master now. |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Looks like the tests failed for a non build problem, I'll take a look tomorrow and see if and how I can fix it :) |
Thank you for all your help @karenbtlai ! |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@karenbtlai Do you think that the code to retrieve the process ID could be broken with TAEF, i.e. if could retrieve the process ID of a process with the same name spawned by TAEF (and MSTest tests happen to work)? |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
d084ee1
to
7c106ae
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Description
This PR enables AXE testing allowing us to essentially run Accessibility Insights on the controls as part of the CI.
Because of that we need two package changes:
Motivation and Context
Allows detecting of a11y issues during development using the a11y detection engine of Accessibility Insights
How Has This Been Tested?
Ran tests in question.
Screenshots (if appropriate):
@YuliKl @ranjesh @StephenLPeters FYI