-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Running the tests using Invoke-Pester rather than using the route via the OneBuild.bat gives me two failures, one for getting the latest nuget.exe path and one for the latest nunit path.
I am loading in the Pester module that is used by OneBuild:
> Import-Module C:\Sandbox\OneBuild\packages\pester.3.0.0-beta2\tools\Pester.psm1
From the OneBuild root, I am then running:
PS C:\Sandbox\OneBuild> Invoke-Pester .\tests
This gives me the two failures:
[-] Should return the full path to to the highest version of NuGet.Commandline found in the solution packages folder 346ms
Expected: {C:\Users\Administrator\AppData\Local\Temp\1\83bfad2e-f926-44c2-bd4f-19a856c7458d\packages\NuGet.CommandLine.2.7.3\tools\nuget.exe}, But was {C:\Users\Administrator\AppData\Local\Temp\1\83bfad
2e-f926-44c2-bd4f-19a856c7458d\packages\NuGet.CommandLine.2.7.2\tools\nuget.exe}
at line: 129 in C:\Sandbox\OneBuild\tests\CommonFunctions.Tests.ps1
and
[-] Should return the full path to to the highest version of NUnit.Runners found in the solution packages folder 313ms
Expected: {C:\Users\Administrator\AppData\Local\Temp\1\a81b2ff3-d9e9-47c0-9770-f341c2c5982e\packages\NUnit.Runners.2.6.3\tools\nunit-console.exe}, But was {C:\Users\Administrator\AppData\Local\Temp\1\a8
1b2ff3-d9e9-47c0-9770-f341c2c5982e\packages\NUnit.Runners.2.6.2\tools\nunit-console.exe}
at line: 161 in C:\Sandbox\OneBuild\tests\CommonFunctions.Tests.ps1
I don't see these if I run via the OneBuild.bat