René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Set-Date don't work and admin-elevated test is silently skipped","articleBody":"1. Currently `Set-Date` tests is silently skipped during elevated test phase in Start-PSPester because the tests use `Test-IsElevated` function instead of `RequireAdminOnWindows` tag.\r\n2. Really if we manually run the test - one is failed:\r\n```powershell\r\nPS \u003e Start-PSPester -Path \\test\\powershell\\Modules\\Microsoft.PowerShell.Utility\\Set-Date.Tests.ps1 -binDir \"C:\\Program Files\\PowerShell\\6.0.0.15\"\r\nVERBOSE: Running pester tests at '\\test\\powershell\\Modules\\Microsoft.PowerShell.Utility\\Set-Date.Tests.ps1'\r\nwith tag 'CI' and ExcludeTag 'Slow'\r\n\r\nDescribing Set-Date\r\n [-] Set-Date should be able to set the date in an elevated context 850ms\r\n   Expected: the expression not to throw an exception. Message was {The parameter is incorrect}\r\n       from \\test\\powershell\\Modules\\Microsoft.PowerShell.Utility\\Set-Date.Tests.ps1:11 char:22\r\n       +         { get-date | set-date } | Should not throw\r\n       +                      ~~~~~~~~\r\n   at line: 11 in \\test\\powershell\\Modules\\Microsoft.PowerShell.Utility\\Set-Date.Tests.ps1\r\n   11:         { get-date | set-date } | Should not throw\r\n [!] Set-Date should produce an error in a non-elevated context 90ms\r\nTests completed in 940ms\r\nPassed: 0 Failed: 1 Skipped: 1 Pending: 0\r\n```\r\nThe command is manually executed failed too (I tested on Windows 10 with PS Core beta 15):\r\n```powershell\r\nPS \u003e get-date | set-date\r\nset-date : The parameter is incorrect\r\nAt line:1 char:12\r\n+ get-date | set-date\r\n+            ~~~~~~~~\r\n    + CategoryInfo          : NotSpecified: (:) [Set-Date], Win32Exception\r\n    + FullyQualifiedErrorId : System.ComponentModel.Win32Exception,Microsoft.PowerShell.Commands.SetDateCommand\r\n\r\nPS \u003e get-date\r\n\r\nSaturday, February 4, 2017 9:09:32 PM\r\n\r\n\r\nPS \u003e set-date\r\n\r\ncmdlet Set-Date at command pipeline position 1\r\nSupply values for the following parameters:\r\nDate: 2/4/2017\r\nset-date : The parameter is incorrect\r\nAt line:1 char:1\r\n+ set-date\r\n+ ~~~~~~~~\r\n    + CategoryInfo          : NotSpecified: (:) [Set-Date], Win32Exception\r\n    + FullyQualifiedErrorId : System.ComponentModel.Win32Exception,Microsoft.PowerShell.Commands.SetDateCommand\r\n```\r\n\r\n\r\n\r\n- [ ] So in [Set-Date.Tests.ps1](https://github.com/PowerShell/PowerShell/blob/master/test/powershell/Modules/Microsoft.PowerShell.Utility/Set-Date.Tests.ps1) the test must be marked by `RequireAdminOnWindows` tag in order to run in admin-elevated phase.\r\nAnd we could remove `Test-IsElevated` from the tests and from `Test.Helpers.psm1`.\r\n\r\n/cc @JamesWTruher @vors \r\n\r\n- [ ] `Set-Date`  requires a fix (for Windows only?).\r\n\r\n/cc @andschwa ","author":{"url":"https://github.com/iSazonov","@type":"Person","name":"iSazonov"},"datePublished":"2017-02-04T18:42:25.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":11},"url":"https://github.com/3099/PowerShell/issues/3099"}