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

Add a Local Test binary, to enable local TerminalApp testing #2294

Merged
merged 7 commits into from
Aug 13, 2019

Conversation

zadjii-msft
Copy link
Member

Summary of the Pull Request

In #1164 we learned that our CI doesn't support WinRT testing. This made us all sad. Since that merged, we haven't really added any TerminalApp tests, because it's a little too hard. You'd have to uncomment the entire file, and if the list of types changed you'd have to manually update the sxs manifest and appxmanifest.

Since that was all insane, I created a new Terminal App unittesting project without those problems.

  1. The project is not named UnitTest*, so the CI won't run it, but it will run locally.
  2. The project will auto-generate its SxS manifest, using the work from Auto-generate our SxS manifest #1987.
  3. We'll use the SxS manifest from step 2 to generate an AppxManifest for running packaged tests.

PR Checklist

  • Closes Re-enable TerminalApp tests SettingsTests and TabsTests #1210
  • CLA signed. If not, go over here and sign the CLA
  • Tests added/passed
  • Requires documentation to be updated
  • I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

I'm 90% just opening this PR to make sure it works in CI.

  * We've got a new unittests project that isn't named *unit*test*

  * We're manually generating the SxS manifest for it. B/C we need to use it at runtime, we need to manually combine it into one manifest file

  * the runas:UAP thing still doesn't work. We'll investigate.
but I'm still stuck with:
```
Summary of Errors Outside of Tests:
Error: TAEF: [HRESULT: 0x80270254] Failed to create the test host process for
out of process test execution. (The
IApplicationActivationManager::ActivateApplication call failed while using a
default host. TAEF's ETW logs which are gathered with the /enableEtwLogging
switch should contain events from relevant providers that may help to diagnose
the failure.)
```
  Frankly just pushing to see if it'll work in CI
tools/GenerateAppxFromManifest.ps1 Show resolved Hide resolved
# Write the modified xml back out.
$appxPrototypeData.save($OutPath)

# Left as a helper for debugging:
Copy link
Contributor

Choose a reason for hiding this comment

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

technically you can make it do this if you pass -debug but that's extra credit. loko up cmdlet binding verbose debug stuff.

@ghost ghost added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Aug 7, 2019
@ghost ghost removed the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Aug 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Re-enable TerminalApp tests SettingsTests and TabsTests
3 participants