Skip to content

Commit

Permalink
Updating Pester on W10 and W2K16 - update - Fix pester#585
Browse files Browse the repository at this point in the history
  • Loading branch information
it-praktyk committed Aug 13, 2017
1 parent 96468d7 commit 62a07d8
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -14,9 +14,9 @@ Pester tests can execute any command or script that is accessible to a Pester te

**Pester also contains a powerful set of mocking functions** in which tests mimic any command functionality within the tested PowerShell code.

Updating Pester on Windows 10
Updating Pester on Windows 10 and Windows Server 2016
-----------
There's a bit of a covfefe with the version of Pester that ships in Windows 10. Microsoft signed the files (which they were required to do), but then PowerShellGet blows up when you try to update the module. Here's the command you need to run in order to get the latest version of Pester the first time on a Windows 10 system:
There's a bit of a confusion with the version of Pester that ships in Windows 10 and Windows Server 2016. These operating systems by default have installed Pester version 3.4.0. Microsoft signed the Pester files (which they were required to do), but then PowerShellGet blows up when you try to update the module. Here's the command you need to run in order to get the latest version of Pester the first time on a Windows 10 system:

`Install-Module Pester -Force -SkipPublisherCheck`

0 comments on commit 62a07d8

Please sign in to comment.