Skip to content

Instantly share code, notes, and snippets.

@rismoney

rismoney/gist:7eaa5f01f56d63c7c726

Created September 8, 2014 20:42
Show Gist options
  • Save rismoney/7eaa5f01f56d63c7c726 to your computer and use it in GitHub Desktop.
Save rismoney/7eaa5f01f56d63c7c726 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
gistfile1.ps1
PS C:\gitrepos\chocolatey> .\build.bat
Build started 9/8/2014 4:36:54 PM.
Project "C:\gitrepos\chocolatey\build.proj" on node 1 (Go target(s)).
Tests:
cmd /c C:\gitrepos\chocolatey\test.cmd
Path is %SystemRoot%\system32\WindowsPowerShell\v1.0\;C:\Tools\Perl64\site\bin;C:\Tools\Perl64\bin;C:\Program Files (
x86)\Common Files\NetSarang;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerS
hell\v1.0\;c:\Chocolatey\bin;C:\Program Files (x86)\Enterprise Vault\EVClient\x64\;C:\@inf\winbuild\scripts;c:\Chocol
atey\bin;C:\Windows\idmu\common;C:\Tools\sysinternals;C:\@inf\winbuild\scripts\;C:\Program Files\Microsoft Network Mo
nitor 3\;C:\Program Files (x86)\vim\vim73;C:\Tools\putty;C:\Tools\csvpng;C:\HashiCorp\Vagrant\bin;C:\Program Files (x
86)\Git\cmd;C:\Program Files (x86)\Git\bin;C:\Program Files (x86)\Puppet Labs\Puppet Enterprise\bin;C:\tools\pester\b
in;C:\Tools\spaz\bin;C:\Program Files (x86)\Puppet Labs\Puppet\bin;C:\Users\rsiegel\appdata\local\scoop\apps\go\1.2\b
in;C:\Users\rsiegel\appdata\local\scoop\shims;C:\Tools\sysinternals;C:\Tools\Python27;C:\Tools\Python27;C:\Tools\Pyth
on27\Scripts;C:\Chocolatey\bin;
The default install location has been changed to 'C:\ProgramData\chocolatey'.
This install will be updated to that location in the next version. It
is strongly suggested you move this installation to the new location
as soon as possible to limit write access from all users. Do not forget
to update PATH & ChocolateyInstall environment variables.
Chocolatey (v0.9.8.27) is installing 'pester' and dependencies. By installing you accept the license for 'pester' and
each dependency you are installing.
pester v2.0.2
Finished installing 'pester' and dependencies - if errors not shown in console, none detected. Check log for errors i
f unsure.
Executing all tests in C:\gitrepos\chocolatey
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Chocolatey-Install
When called with parameters
[+] should send params to Chocolatey-NuGet 1ms
When called normally
[+] should not call Chocolatey-PackagesConfig 95ms
[+] should not call Chocolatey-WebPI 61ms
[+] should not call Chocolatey-WindowsFeatures 60ms
[+] should not call Chocolatey-RubyGem 60ms
[+] should call Chocolatey-NuGet 60ms
When called with .config in the name but not ending in .config
[+] should not call Chocolatey-PackagesConfig 63ms
[+] should not call Chocolatey-WebPI 61ms
[+] should not call Chocolatey-WindowsFeatures 62ms
[+] should not call Chocolatey-RubyGem 59ms
[+] should call Chocolatey-NuGet 60ms
When called from a manifest named packages.config
[+] should call Chocolatey-PackagesConfig 60ms
[+] should not call Chocolatey-WebPI 59ms
[+] should not call Chocolatey-WindowsFeatures 59ms
[+] should not call Chocolatey-RubyGem 60ms
[+] should not call Chocolatey-NuGet 60ms
When called from a manifest named MyChocolateyPackages.config
[+] should call Chocolatey-PackagesConfig 61ms
[+] should not call Chocolatey-WebPI 60ms
[+] should not call Chocolatey-WindowsFeatures 60ms
[+] should not call Chocolatey-RubyGem 59ms
[+] should not call Chocolatey-NuGet 59ms
With ruby as the source
[+] should not call Chocolatey-PackagesConfig 60ms
[+] should not call Chocolatey-WebPI 59ms
[+] should not call Chocolatey-WindowsFeatures 61ms
[+] should call Chocolatey-RubyGem 62ms
[+] should not call Chocolatey-NuGet 61ms
With webpi as the source
[+] should not call Chocolatey-PackagesConfig 60ms
[+] should call Chocolatey-WebPI 60ms
[+] should not call Chocolatey-WindowsFeatures 59ms
[+] should not call Chocolatey-RubyGem 61ms
[+] should not call Chocolatey-NuGet 61ms
With windowsfeatures as the source
[+] should not call Chocolatey-PackagesConfig 60ms
[+] should not call Chocolatey-WebPI 61ms
[+] should call Chocolatey-WindowsFeatures 61ms
[+] should not call Chocolatey-RubyGem 60ms
[+] should not call Chocolatey-NuGet 61ms
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Chocolatey-InstallIfMissing
When called with no version and package exists locally
EXEC : warning : installmissing command is deprecated and will be removed. Install provides the same functionality now.
[C:\gitrepos\chocolatey\build.proj]
[+] should not call Chocolatey-Version 60ms
[+] should not call Chocolatey-Nuget 72ms
When called with no version and package does not exist locally
EXEC : warning : installmissing command is deprecated and will be removed. Install provides the same functionality now.
[C:\gitrepos\chocolatey\build.proj]
[+] should call Chocolatey-Version 60ms
When called with a version and the package does not exist locally
EXEC : warning : installmissing command is deprecated and will be removed. Install provides the same functionality now.
[C:\gitrepos\chocolatey\build.proj]
[+] should call Chocolatey-Nuget 62ms
When called with a version and version is different than the one in the repo
EXEC : warning : installmissing command is deprecated and will be removed. Install provides the same functionality now.
[C:\gitrepos\chocolatey\build.proj]
[+] should call Chocolatey-Nuget 60ms
When called with a version that is the same as the one in the repo
EXEC : warning : installmissing command is deprecated and will be removed. Install provides the same functionality now.
[C:\gitrepos\chocolatey\build.proj]
[+] should not call Chocolatey-Nuget 61ms
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Chocolatey-NuGet
under normal circumstances
Chocolatey (v0.9.8.28-alpha2) is installing 'somepackage' and dependencies. By installing you accept the license for
'somepackage' and each dependency you are installing.
Finished installing 'somepackage' and dependencies - if errors not shown in console, none detected. Check log for err
ors if unsure.
[+] should call Run-NuGet 1ms
[+] should call Update-SessionEnvironment 60ms
with packageName 'all'
[+] should call Chocolatey-InstallAll 1ms
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Chocolatey-PackagesConfig
With a packages.config manifest that exists
=====================================================
Installing packages from manifest: 'TestDrive:\packages.config'
=====================================================
[+] should execute the contents of the packages.config 0ms
[+] should call Chocolatey-Install 1ms
[+] should not call Chocolatey-NuGet 60ms
With a packages.config manifest that does not exist
[+] should do nothing 0ms
[+] should not call Chocolatey-Install 60ms
[+] should not call Chocolatey-NuGet 60ms
With a .config manifest that is named MyChocolateyPackages.config
=====================================================
Installing packages from manifest: 'TestDrive:\MyChocolateyPackages.config'
=====================================================
[+] should treat it like a packages.config 0ms
[+] should call Chocolatey-Install 1ms
[+] should not call Chocolatey-Nuget 59ms
With a package name ending with .config without a '\' in the name
[+] should treat it like a regular package 0ms
[+] should not call Chocolatey-Install 60ms
[+] should call Chocolatey-NuGet 1ms
With a packages.config manifest missing package id
=====================================================
Installing packages from manifest: 'TestDrive:\packages.config'
=====================================================
[+] should only call Chocolatey-Install on packages that have specified an Id 0ms
[+] should not call Chocolatey-Install 59ms
[+] should not call Chocolatey-NuGet 59ms
With a packages.config manifest with badly formed xml
=====================================================
Installing packages from manifest: 'TestDrive:\packages.config'
=====================================================
[+] should error upon getting content 0ms
[+] should return an error 3ms
[+] should not call Chocolatey-Install 60ms
[+] should not call Chocolatey-NuGet 61ms
With a packages.config manifest with no versions
=====================================================
Installing packages from manifest: 'TestDrive:\packages.config'
=====================================================
[+] should execute the contents of the packages.config 0ms
[+] should call Chocolatey-Install 1ms
[+] should not call Chocolatey-Nuget 60ms
When calling Chocolatey-PackagesConfig with a packages.config manifest that has installArguments
=====================================================
Installing packages from manifest: 'TestDrive:\packages.config'
=====================================================
[+] should execute the contents of the packages.config 0ms
[+] should call Chocolatey-Install 1ms
[+] should not call Chocolatey-Nuget 60ms
When calling Chocolatey-PackagesConfig with a packages.config manifest that has no installArguments attribute
=====================================================
Installing packages from manifest: 'TestDrive:\packages.config'
=====================================================
[+] should execute the contents of the packages.config 0ms
[+] should call Chocolatey-Install 1ms
[+] should not call Chocolatey-Nuget 62ms
With a packages.config manifest that has ruby packages
=====================================================
Installing packages from manifest: 'TestDrive:\packages.config'
=====================================================
[+] should execute the contents of the packages.config 0ms
[+] should call Chocolatey-Install 1ms
[+] should not call Chocolatey-Nuget 60ms
With a packages.config manifest that has webpi packages
=====================================================
Installing packages from manifest: 'TestDrive:\packages.config'
=====================================================
[+] should execute the contents of the packages.config 0ms
[+] should call Chocolatey-Install 2ms
[+] should not call Chocolatey-Nuget 60ms
With a packages.config manifest that has windowsfeatures packages
=====================================================
Installing packages from manifest: 'TestDrive:\packages.config'
=====================================================
[+] should execute the contents of the packages.config 0ms
[+] should call Chocolatey-Install 1ms
[+] should not call Chocolatey-Nuget 61ms
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Chocolatey-Uninstall
When no PackageName parameter is passed to this function
[+] should return an error 60ms
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Chocolatey-Update
When updating a folder that has a prerelease version
Nothing to update.
[+] should not error 0ms
when updating a folder that has a prerelease version with multiple dashes
Nothing to update.
[+] should not error 0ms
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Get-ChecksumValid
When a good checksum is provided
[+] should not return an error 1ms
When a good checksum and checksum type sha1 is provided
[+] should not return an error 1ms
When a good checksum and bad checksum type is provided
[+] should default to md5 and validate against that 0ms
[+] should not return an error 1ms
When a bad checksum is provided
[+] should error 1ms
[+] should error with the correct message 1ms
When a bad checksum with checksum type sha1 is provided
[+] should error 1ms
[+] should error with the correct message 1ms
When an invalid checksum type is provided
[+] should error 1ms
[+] should error with message containing checksum type 'md5' 1ms
When no checksum is provided
[+] should not error 1ms
[+] should not call checksum to verify 59ms
When no checksum is provided and the file does not exist
[+] should not error 1ms
[+] should not call checksum to verify 58ms
When a checksum is provided but the file doesn't exist
[+] should error 1ms
[+] should error with the correct message 1ms
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Get-ChocolateyUnzip
When a valid zip file is provided
Everything is Ok
Extracting C:\Users\rsiegel\AppData\Local\Temp\pester\some\file.zip to C:\Users\rsiegel\AppData\Local\Temp\pester\des
t...
C:\Users\rsiegel\AppData\Local\Temp\pester\dest
[+] should not return an error 1ms
[+] should extract files from the archive 2ms
[+] should extract files with correct content 3ms
When a nonexistent destination path is provided
Everything is Ok
Extracting C:\Users\rsiegel\AppData\Local\Temp\pester\some\file.zip to C:\Users\rsiegel\AppData\Local\Temp\pester\non
existentdir...
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 09/08/2014 16:37 nonexistentdir
C:\Users\rsiegel\AppData\Local\Temp\pester\nonexistentdir
[+] should not return an error 3ms
[+] should create the destination directory 2ms
[+] should extract files from the archive 2ms
When a nonexistent archive file is specified
Extracting C:\Users\rsiegel\AppData\Local\Temp\pester\nonexistentfile.zip to C:\Users\rsiegel\AppData\Local\Temp\pest
er\dest...
7-Zip encountered a fatal error while extracting the files
[+] should throw an exception 2ms
When an invalid/corrupted zip file is provided
Extracting C:\Users\rsiegel\AppData\Local\Temp\pester\invalidzipfile.zip to C:\Users\rsiegel\AppData\Local\Temp\peste
r\dest...
7-Zip encountered a fatal error while extracting the files
[+] should throw an exception 2ms
When the archive is under System32
Everything is Ok
Extracting C:\Windows\System32\config\systemprofile\AppData\Local\Temp\file.zip to C:\Users\rsiegel\AppData\Local\Tem
p\pester\dest...
C:\Users\rsiegel\AppData\Local\Temp\pester\dest
[+] should not return an error 1ms
[+] should extract files from the archive 2ms
When the destination path is inside System32
Everything is Ok
Extracting C:\Users\rsiegel\AppData\Local\Temp\pester\some\file.zip to C:\Windows\System32\config\systemprofile\AppDa
ta\Local\Temp\chocolatey-test...
d---- 09/08/2014 16:37 chocolatey-test
C:\Windows\System32\config\systemprofile\AppData\Local\Temp\chocolatey-test
[+] should not return an error 1ms
[+] should extract files from the archive 3ms
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Get-ConfigValue
when retrieving a simple return value
[+] should not be null 1ms
[+] should return the result of what we specified 1ms
when retrieving a list
[+] should not be null 1ms
[+] should return a type of what we specified 1ms
[+] should contain the same number of sources as specified 2ms
[+] should contain source IDs that are not null or empty 2ms
[+] should contain source values that are not null or empty 2ms
[+] should contain a source for chocolatey 1ms
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Get-LongPackageVersion
under normal circumstances
[+] should return a long version string with 12 fields of padding back 1ms
when version has a date value
[+] should not error 0ms
[+] should return a long version string that includes all of the date string 1ms
when there is a prerelease package version
[+] should not error 0ms
[+] should return a long version string that includes the prerelease information as the last element 1ms
when there is a prerelease package version that contains multiple dashes
[+] should not error 0ms
[+] should return a long version string that includes the prerelease information as the last element 1ms
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Get-PackageFoldersForPackage
under normal circumstances
[+] should find that the folder path actually exists 1ms
[+] should return a package folder back 1ms
when folder version has a date value
[+] should not error 0ms
[+] should return a package folder back 1ms
when folder has a prerelease version
[+] should not error 0ms
[+] should return a package folder back 1ms
when folder has a prerelease version with multiple dashes
[+] should not error 0ms
[+] should return a package folder back 1ms
when multiple versions are installed
[+] should return multiple package folders back 3ms
when multiple versions are installed and other packages
[+] should return multiple package folders back 2ms
[+] should not return the package that is not the same name 2ms
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Get-PackageFolderVersion
under normal circumstances
[+] should return the output of Get-VersionsForComparison 1ms
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Get-ProcessorBits
when calling with no arguments
[+] should return the correct bitness 1ms
when comparing against the bitness and they are equal
[+] should return true 1ms
when comparing against the bitness are not equal
[+] should return false 1ms
Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
Describing Get-VersionsForComparison
under normal circumstances
[+] should call Get-LongPackageVersion 0ms
[+] should have one item returned 1ms
[+] should return both versions back as the first element in a hash 1ms
[+] should return the short version back as the value of the first element in the hash 1ms
when passed the same version multiple times
[+] should work appropriately 0ms
[+] should only have one item returned 1ms
with a prerelease package
[+] should work appropriately 0ms
[+] should return versions in the first element 1ms
with multiple prerelease packages of the same underlying version
[+] should work appropriately 0ms
[+] should return the long version of the first short version 1ms
[+] should return the long version of the second short version 1ms
Describing Initialize-Chocolatey
When installing as admin, with $Env:ChocolateyInstall not set and no arguments
Creating ChocolateyInstall as an Environment variable (targeting 'Machine') and setting it to 'C:\ProgramData\chocola
tey'
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\ProgramData\chocolatey'.
The packages themselves go to 'C:\ProgramData\chocolatey\lib' (i.e. C:\ProgramData\chocolatey\lib\yourPackageName).
A shim file for the command line goes to 'C:\ProgramData\chocolatey\bin' and points to an executable in 'C:\ProgramDa
ta\chocolatey\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\ProgramData\ch
ocolatey'.
PATH environment variable does not have C:\ProgramData\chocolatey\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should create ChocolateyInstall at Process scope 2ms
[+] should not ChocolateyInstall at User scope 2ms
[+] should create ChocolateyInstall at Machine scope 2ms
When installing as admin, with $Env:ChocolateyInstall not set, with explicit chocolateyPath
Creating ChocolateyInstall as an Environment variable (targeting 'Machine') and setting it to 'C:\Users\rsiegel\AppDa
ta\Local\Temp\pester\chocoinstall'
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should create ChocolateyInstall at Process scope 2ms
[+] should not ChocolateyInstall at User scope 2ms
[+] should create ChocolateyInstall at Machine scope 2ms
When installing as admin, with $Env:ChocolateyInstall set at Process scope, with same explicit chocolateyPath
Creating ChocolateyInstall as an Environment variable (targeting 'Machine') and setting it to 'C:\Users\rsiegel\AppDa
ta\Local\Temp\pester\chocoinstall'
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 6ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should not create ChocolateyInstall at User scope 2ms
[+] should create ChocolateyInstall at Machine scope 2ms
When installing as admin, with $Env:ChocolateyInstall set at Process scope, with different explicit chocolateyPath
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should not create ChocolateyInstall at User scope 2ms
[+] should not create ChocolateyInstall at Machine scope 2ms
When installing as admin with $Env:ChocolateyInstall set at Machine scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should not create ChocolateyInstall at User scope 2ms
[+] should preserve value of ChocolateyInstall at Machine scope 2ms
When installing as admin with $Env:ChocolateyInstall set at User scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 2ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should preserve value of ChocolateyInstall at User scope 2ms
[+] should not create ChocolateyInstall at Machine scope 2ms
When installing as admin with $Env:ChocolateyInstall set at Process scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should not create ChocolateyInstall at User scope 2ms
[+] should not create ChocolateyInstall at Machine scope 2ms
When installing as admin with $Env:ChocolateyInstall set at Machine scope and same at User scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 6ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should preserve value of ChocolateyInstall at User scope 2ms
[+] should preserve value of ChocolateyInstall at Machine scope 2ms
When installing as admin with $Env:ChocolateyInstall set at Machine scope and different at User scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should preserve value of ChocolateyInstall at User scope 2ms
[+] should preserve value of ChocolateyInstall at Machine scope 2ms
When installing as admin with $Env:ChocolateyInstall set at Machine scope and different at Process scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 2ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should not create ChocolateyInstall at User scope 2ms
[+] should preserve value of ChocolateyInstall at Machine scope 2ms
When installing as admin with $Env:ChocolateyInstall set at User scope and different at Process scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 2ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should preserve value of ChocolateyInstall at User scope 2ms
[+] should not create ChocolateyInstall at Machine scope 2ms
When installing as admin with bin directory not on PATH
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should add bin to PATH at Process scope 4ms
[+] should not add bin to PATH at User scope 2ms
[+] should add bin to PATH at Machine scope 4ms
When installing as admin with bin directory on PATH at Machine scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should retain bin on PATH at Process scope 4ms
[+] should not add bin to PATH at User scope 2ms
[+] should retain bin on PATH at Machine scope 4ms
When installing as admin with bin directory on PATH at User scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should retain bin on PATH at Process scope 4ms
[+] should retain bin on PATH at User scope 2ms
[+] should not add bin to PATH at Machine scope 3ms
When installing as simulated standard user, with $Env:ChocolateyInstall not set and no arguments
Creating ChocolateyInstall as an Environment variable (targeting 'User') and setting it to 'C:\ProgramData\chocolatey
'
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\ProgramData\chocolatey'.
The packages themselves go to 'C:\ProgramData\chocolatey\lib' (i.e. C:\ProgramData\chocolatey\lib\yourPackageName).
A shim file for the command line goes to 'C:\ProgramData\chocolatey\bin' and points to an executable in 'C:\ProgramDa
ta\chocolatey\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\ProgramData\ch
ocolatey'.
PATH environment variable does not have C:\ProgramData\chocolatey\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should create ChocolateyInstall at Process scope 2ms
[+] should create ChocolateyInstall at User scope 2ms
[+] should not create ChocolateyInstall at Machine scope 2ms
When installing as simulated standard user, with $Env:ChocolateyInstall not set, with explicit chocolateyPath
Creating ChocolateyInstall as an Environment variable (targeting 'User') and setting it to 'C:\Users\rsiegel\AppData\
Local\Temp\pester\chocoinstall'
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should create ChocolateyInstall at Process scope 2ms
[+] should create ChocolateyInstall at User scope 2ms
[+] should not create ChocolateyInstall at Machine scope 2ms
When installing as simulated standard user, with $Env:ChocolateyInstall set at Process scope, with same explicit ch
ocolateyPath
Creating ChocolateyInstall as an Environment variable (targeting 'User') and setting it to 'C:\Users\rsiegel\AppData\
Local\Temp\pester\chocoinstall'
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should create ChocolateyInstall at User scope 2ms
[+] should not create ChocolateyInstall at Machine scope 2ms
When installing as simulated standard user, with $Env:ChocolateyInstall set at Process scope, with different explic
it chocolateyPath
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should not create ChocolateyInstall at User scope 2ms
[+] should not create ChocolateyInstall at Machine scope 2ms
When installing as simulated standard user with $Env:ChocolateyInstall set at Machine scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 2ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should not create ChocolateyInstall at User scope 2ms
[+] should preserve value of ChocolateyInstall at Machine scope 2ms
When installing as simulated standard user with $Env:ChocolateyInstall set at User scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should preserve value of ChocolateyInstall at User scope 2ms
[+] should not create ChocolateyInstall at Machine scope 2ms
When installing as simulated standard user with $Env:ChocolateyInstall set at Process scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 2ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should not create ChocolateyInstall at User scope 2ms
[+] should not create ChocolateyInstall at Machine scope 2ms
When installing as simulated standard user with $Env:ChocolateyInstall set at Machine scope and same at User scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 2ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 3ms
[+] should preserve value of ChocolateyInstall at User scope 2ms
[+] should preserve value of ChocolateyInstall at Machine scope 2ms
When installing as simulated standard user with $Env:ChocolateyInstall set at Machine scope and different at User s
cope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should preserve value of ChocolateyInstall at User scope 2ms
[+] should preserve value of ChocolateyInstall at Machine scope 2ms
When installing as simulated standard user with $Env:ChocolateyInstall set at Machine scope and different at Proces
s scope
We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables
/application packages, not library packages.
That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rsiegel\AppData\Local\Temp\peste
r\chocoinstall'.
The packages themselves go to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rsiegel\Ap
pData\Local\Temp\pester\chocoinstall\lib\yourPackageName).
A shim file for the command line goes to 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin' and points to
an executable in 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.
Creating Chocolatey NuGet folders if they do not already exist.
Copying the contents of 'C:\Users\rsiegel\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rsiegel\
AppData\Local\Temp\pester\chocoinstall'.
PATH environment variable does not have C:\Users\rsiegel\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
Chocolatey is now ready.
You can call chocolatey from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
[+] should create installation directory 1ms
[+] should create expected subdirectories 5ms
[+] should copy files to expected locations 5ms
[+] should preserve value of ChocolateyInstall at Process scope 2ms
[+] should not create ChocolateyInstall at User scope 2ms
[+] should preserve value of ChocolateyInstall at Machine scope 2ms
Attempting to cancel the build...
C:\gitrepos\chocolatey\build.proj(17,5): warning MSB5021: The task executable is being terminated due to cancellation o
f the build.
Done Building Project "C:\gitrepos\chocolatey\build.proj" (Go target(s)) -- FAILED.
Build FAILED.
"C:\gitrepos\chocolatey\build.proj" (Go target) (1) ->
(Tests target) ->
EXEC : warning : installmissing command is deprecated and will be removed. Install provides the same functionality no
w. [C:\gitrepos\chocolatey\build.proj]
EXEC : warning : installmissing command is deprecated and will be removed. Install provides the same functionality no
w. [C:\gitrepos\chocolatey\build.proj]
EXEC : warning : installmissing command is deprecated and will be removed. Install provides the same functionality no
w. [C:\gitrepos\chocolatey\build.proj]
EXEC : warning : installmissing command is deprecated and will be removed. Install provides the same functionality no
w. [C:\gitrepos\chocolatey\build.proj]
EXEC : warning : installmissing command is deprecated and will be removed. Install provides the same functionality no
w. [C:\gitrepos\chocolatey\build.proj]
C:\gitrepos\chocolatey\build.proj(17,5): warning MSB5021: The task executable is being terminated due to cancellation
of the build.
6 Warning(s)
0 Error(s)
Time Elapsed 00:02:45.95
Terminate batch job (Y/N)? y
@ferventcoder
Copy link 

 Creating Chocolatey NuGet folders if they do not already exist.

  Copying the contents of 'C:\Users\rob\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rob\AppData\Local\T
  emp\pester\chocoinstall'.
  PATH environment variable does not have C:\Users\rob\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
  Chocolatey is now ready.
  You can call chocolatey from anywhere, command line or powershell by typing choco.
  Run choco /? for a list of functions.
  You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
  [+]    should create installation directory 2ms
  [+]    should create expected subdirectories 6ms
  [+]    should copy files to expected locations 4ms
  [+]    should preserve value of ChocolateyInstall at Process scope 2ms
  [+]    should preserve value of ChocolateyInstall at User scope 2ms
  [+]    should not create ChocolateyInstall at Machine scope 2ms
    When installing as simulated standard user with bin directory not on PATH
  We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables/applic
  ation packages, not library packages.
  That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rob\AppData\Local\Temp\pester\chocoinst
  all'.
  The packages themselves go to 'C:\Users\rob\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rob\AppData\Local\Tem
  p\pester\chocoinstall\lib\yourPackageName).
  A shim file for the command line goes to 'C:\Users\rob\AppData\Local\Temp\pester\chocoinstall\bin' and points to an executab
  le in 'C:\Users\rob\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.

  Creating Chocolatey NuGet folders if they do not already exist.

  Copying the contents of 'C:\Users\rob\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rob\AppData\Local\T
  emp\pester\chocoinstall'.
  PATH environment variable does not have C:\Users\rob\AppData\Local\Temp\pester\chocoinstall\bin in it. Adding...
  Chocolatey is now ready.
  You can call chocolatey from anywhere, command line or powershell by typing choco.
  Run choco /? for a list of functions.
  You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
  [+]    should add bin to PATH at Process scope 4ms
  [+]    should add bin to PATH at User scope 2ms
  [+]    should not add bin to PATH at Machine scope 3ms
    When installing as simulated standard user with bin directory on PATH at Machine scope
  We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables/applic
  ation packages, not library packages.
  That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rob\AppData\Local\Temp\pester\chocoinst
  all'.
  The packages themselves go to 'C:\Users\rob\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rob\AppData\Local\Tem
  p\pester\chocoinstall\lib\yourPackageName).
  A shim file for the command line goes to 'C:\Users\rob\AppData\Local\Temp\pester\chocoinstall\bin' and points to an executab
  le in 'C:\Users\rob\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.

  Creating Chocolatey NuGet folders if they do not already exist.

  Copying the contents of 'C:\Users\rob\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rob\AppData\Local\T
  emp\pester\chocoinstall'.
  Chocolatey is now ready.
  You can call chocolatey from anywhere, command line or powershell by typing choco.
  Run choco /? for a list of functions.
  You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
  [+]    should retain bin on PATH at Process scope 4ms
  [+]    should not add bin to PATH at User scope 2ms
  [+]    should retain bin on PATH at Machine scope 3ms
    When installing as simulated standard user with bin directory on PATH at User scope
  We are setting up the Chocolatey repository for NuGet packages that should be at the machine level. Think executables/applic
  ation packages, not library packages.
  That is what Chocolatey NuGet goodness is for. The repository is set up at 'C:\Users\rob\AppData\Local\Temp\pester\chocoinst
  all'.
  The packages themselves go to 'C:\Users\rob\AppData\Local\Temp\pester\chocoinstall\lib' (i.e. C:\Users\rob\AppData\Local\Tem
  p\pester\chocoinstall\lib\yourPackageName).
  A shim file for the command line goes to 'C:\Users\rob\AppData\Local\Temp\pester\chocoinstall\bin' and points to an executab
  le in 'C:\Users\rob\AppData\Local\Temp\pester\chocoinstall\lib\yourPackageName'.

  Creating Chocolatey NuGet folders if they do not already exist.

  Copying the contents of 'C:\Users\rob\AppData\Local\Temp\pester\chocotmp\chocolateyInstall' to 'C:\Users\rob\AppData\Local\T
  emp\pester\chocoinstall'.
  Chocolatey is now ready.
  You can call chocolatey from anywhere, command line or powershell by typing choco.
  Run choco /? for a list of functions.
  You may need to shut down and restart powershell and/or consoles first prior to using chocolatey.
  [+]    should retain bin on PATH at Process scope 4ms
  [+]    should retain bin on PATH at User scope 3ms
  [+]    should not add bin to PATH at Machine scope 3ms
  Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
  Describing Install-ChocolateyDesktopLink
    When no TargetFilePath parameter is passed to this function
  [+]    should return an error 34ms
    When TargetFilePath is to a location that does not exist
  [+]    should return an error 34ms
    When valid targetpath is provided
  Install-ChocolateyShortcut completed has finished successfully! The chocolatey gods have answered your request!
  [+]    should succeed, and desktop shortcut is created. 1ms
  Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
  Describing Install-ChocolateyInstallPackage
    When file type is msu
  Installing package...
  package has been installed.
  [+]    should be installed 36ms
  Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
  Describing Install-ChocolateyShortcut
    When no ShortCutFilePath parameter is passed to this function
  [+]    should return an error 43ms
    When no TargetPath parameter is passed to this function
  [+]    should return an error 37ms
    When TargetPath is a location that does not exist
  [+]    should return an error 38ms
    When a Working Directory is provided, and this parth doesn't exist
  [+]    should return an error 39ms
    When an IconLocation is provided, and the path doesn't exist
  [+]    should return an error 35ms
    When valid shortcutpath and targetpath are provided
  Install-ChocolateyShortcut completed has finished successfully! The chocolatey gods have answered your request!
  [+]    should succeed. 1ms
    When all parameters are passed with valid values
  Install-ChocolateyShortcut completed has finished successfully! The chocolatey gods have answered your request!
  [+]    should succeed. 0ms
  Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
  Describing Install-ChocolateyVsixPackage
    When not Specifying a version and version 9, 10 and 11 is installed
  [+]    should install for version 11 37ms
    When not Specifying a version and only 10 is installed
  [+]    should install for version 10 36ms
    When Specifying a specific version that version is installed
  [+]    should install for version 10 if 10 is specified 36ms
    When VS is not installed
  [+]    should fail 37ms
    When the specified version of VS is not installed
  [+]    should fail 33ms
    When something goes wrong downloading the file
  [+]    should fail 35ms
    When Installed VS version is less than 10
  [+]    should fail 34ms
    When Installer returns an exit code error
  [+]    should fail 34ms
    When VSIX is already installed
  [+]    should succeed 39ms
    When package name has spaces
  [+]    should remove spaces 34ms
  Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
  Describing Run-ChocolateyPS1
    with installer arguments
  [+]    should set chocolateyInstallArguments env var to Installer Arguments 1ms
  Please run chocolatey /? or chocolatey help - chocolatey v0.9.8.28-alpha2
  Describing Update-SessionEnvironment
    under normal circumstances
  [+]    should properly refresh MACHINE variables set outside this session 1ms
  [+]    should properly refresh USER variables set outside this session overriding Machine vars with same key 1ms
  [+]    should properly refresh the PATH variable concatenating MACHINE and USER 1ms
  Tests completed in 3.62s
  Passed: 317 Failed: 0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment