Skip to content
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

MUXTestInfra refactor #3212

Merged
merged 35 commits into from Sep 10, 2020
Merged

MUXTestInfra refactor #3212

merged 35 commits into from Sep 10, 2020

Conversation

azchohfi
Copy link
Contributor

Description

This work refactors MUX's test infrastructure and decouples it into an easier to use nuget package that can be leveraged by other app developers (e.g. the Windows Community Toolkit) to create tests that build for both MSTest and TAEF.

This PR now generates 3 new nuget packages:

  1. MUXAppTestHelpers
  2. MUXTestInfra.MSTest
  3. MUXTestInfra.TAEF

Motivation and Context

Share UI test infra structure with WCT, to make it easier to move a control from the WCT to WinUI.

How Has This Been Tested?

Both on MUX (both running TAEF tests locally and MSTest thru VS 16.7) and on the WCT (https://github.com/windows-toolkit/WindowsCommunityToolkit/tree/muxtestinfra)

@msft-github-bot msft-github-bot added the needs-triage Issue needs to be triaged by the area owners label Aug 28, 2020
MUXControls.sln Outdated Show resolved Hide resolved
MUXControlsInnerLoop.sln Outdated Show resolved Hide resolved
@azure-pipelines
Copy link

Commenter does not have sufficient privileges for PR 3212 in repo microsoft/microsoft-ui-xaml

@kmahone
Copy link
Member

kmahone commented Sep 2, 2020

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@StephenLPeters
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kmahone
Copy link
Member

kmahone commented Sep 2, 2020

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kmahone
Copy link
Member

kmahone commented Sep 3, 2020

We are running into some unexplained build pipeline issues.
@StephenLPeters is working on a fix in #3223.

Hopefully once that goes though you will be able to merge master and avoid these build breaks.

@StephenLPeters
Copy link
Contributor

@azchohfi The pipeline fix just went in, could you please merge master into this PR?

@azchohfi
Copy link
Contributor Author

azchohfi commented Sep 3, 2020

Absolutely!

@kmahone
Copy link
Member

kmahone commented Sep 3, 2020

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kmahone
Copy link
Member

kmahone commented Sep 4, 2020

The tests are all passing on 19H1. But they are failing on RS5 and lower. Looks like a crash in AppTestAutomationHelpers.dll.

My guess is that we are calling an api that was adding only in 19H1, and we need to include some platform version checks.

@azchohfi
Copy link
Contributor Author

azchohfi commented Sep 9, 2020

@kmahone or @StephenLPeters, could you please trigger a new build? I think it should be fine now.

@kmahone
Copy link
Member

kmahone commented Sep 9, 2020

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kmahone kmahone merged commit c46d28b into microsoft:master Sep 10, 2020
@azchohfi azchohfi deleted the user/azchohfi/testinfra branch September 10, 2020 19:00
{
InstallCert(Path.Combine(deploymentDir, packageName + ".cer"));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this may have broke the release pipeline because the cert file wasn't found

ghost pushed a commit to CommunityToolkit/WindowsCommunityToolkit that referenced this pull request Oct 16, 2020
WCT is now sharing WinUI's test infrastructure. This is the continuation of the work on this PR microsoft/microsoft-ui-xaml#3212.

## PR Type
What kind of change does this PR introduce?
- Feature
- Build or CI related changes 

## What is the current behavior?
No UI Tests.

## What is the new behavior?
Added simple UI Tests for the WCT that use the same shared infrastructure used by WinUI. This will enable us to move controls/helpers in an easier way from the WCT->WinUI in the future.

## PR Checklist

Please check if your PR fulfills the following requirements:

- [X] Tested code with current [supported SDKs](../readme.md#supported)
- [ ] Pull Request has been submitted to the documentation repository [instructions](..\contributing.md#docs). Link: <!-- docs PR link -->
- [ ] Sample in sample app has been added / updated (for bug fixes / features)
    - [ ] Icon has been created (if new sample) following the [Thumbnail Style Guide and templates](https://github.com/windows-toolkit/WindowsCommunityToolkit-design-assets)
- [X] Tests for the changes have been added (for bug fixes / features) (if applicable)
- [X] Header has been added to all new source files (run *build/UpdateHeaders.bat*)
- [X] Contains **NO** breaking changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-DevInternal Internal build infrastructure, code cleanup, engineering efficiency team-Controls Issue for the Controls team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants