You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tests on windows should not fail, when they run in non-elevated (non admin) env #1486
There is a number of tests (mostly in PackageManager) that are failing, when they run without admin priviledges. Our CI doesn't catch it, because it's run elevated. But we should have a good experience for developers: they should be able to run it locally without elevation and see clean results on the build from master.
changed the title [-]Tests on windows should not fail, when they run in non-elevated env [/-][+]Tests on windows should not fail, when they run in non-elevated (non admin) env [/+]on Jul 22, 2016
Introduce a new tag for Pester tests (i.e. "RequireAdmin").
Mark tests that absolutely has to be admin with this tag.
Change the rest of the tests to avoid requiring admin privileges.
In the AppVeyor CI split CoreCLR test run into two parts:
-ExcludeTag 'RequireAdmin' (this should be executed with down-graded elevation, for example )
Activity
[-]Tests on windows should not fail, when they run in non-elevated env [/-][+]Tests on windows should not fail, when they run in non-elevated (non admin) env [/+]vors commentedon Sep 10, 2016
My current proposition about it:
Mark tests that absolutely has to be admin with this tag.
Change the rest of the tests to avoid requiring admin privileges.
-ExcludeTag 'RequireAdmin'(this should be executed with down-graded elevation, for example )-Tag 'RequireAdmin'with normal admin priviledgesThoughts? cc Steve Lee (@SteveL-MSFT) James Truher (@JamesWTruher) Andy Jordan (@andschwa) Jason Shirk (@lzybkr)
SteveL-MSFT commentedon Sep 12, 2016
Seems reasonable. Generally speaking, we shouldn't require admin for anything that doesn't require admin including running tests.