Add tests for configure mixed elevation #4487
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| } | ||
|
|
||
| /// <summary> | ||
| /// Verifies that creating a high integrity unit processor. Must run elevated. |
There was a problem hiding this comment.
I don't want a test that will actually request admin. The basic test should still use the test mode, with two units (one high, one medium) and a special resource that writes the PID into a target file so that you can ensure that they were routed to different set processors.
There was a problem hiding this comment.
I changed the tests so that it checks how many unique PIDs are created when applying an elevated and non elevated unit.
| /// </summary> | ||
| [Collection("UnitTestCollection")] | ||
| [OutOfProc] | ||
| [OutOfProcOnly] |
There was a problem hiding this comment.
I assume that these tests still attempt to run if you select everything in the Test Explorer? I'm not sure how to default them to not selected, but that would be better if we can.
There was a problem hiding this comment.
I was not able to find a way to have these skipped in Test Explorer. There is an option to do something like Fact[Skip="reason"] but that causes the test to always be skipped.
src/Microsoft.Management.Configuration.UnitTests/Tests/ConfigurationMixedElevationTests.cs
Outdated
Show resolved
Hide resolved
src/Microsoft.Management.Configuration.UnitTests/Tests/ConfigurationMixedElevationTests.cs
Show resolved
Hide resolved
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Adds a test that runs two configuration with different elevation requirements using the dynamic runtime factory through COM.
I attempted to try different scenarios that would override the flows, but since the tests are running elevated, I wasn't able to succesfully reproduce the failures in the build machine.
Microsoft Reviewers: Open in CodeFlow