Appveyor test runs on Windows has PShome path is pointing to
C:\projects\powershell\src\powershell-win-core\bin\Release\netcoreapp1.0\win81-x64\publish
However on Travis CI test runs, the PSHome path is pointing to the root folder.
/home/travis/build/PowerShell/PowerShell/src/powershell-unix/bin/Linux/netcoreapp1.0/ubuntu.14.04-x64
This means that appveryor runs under ..\publish folder but travisCI runs under one level up.
Are tests supposed to be running under ..\publish folder?
To workaround this problem I have to restore PackageManagement and PowerShellGet modules during build time to publish folder and one level up.
I think the fix should be in start-pspester.
Steps to reproduce
Add $PSHome $env:PSModulePath to one of your checkin test and watch the output
Expected behavior
Tests are supposed to be running under ..\publish folder
Actual behavior
Described above.
Environment data
Alpha.12
Appveyor test runs on Windows has PShome path is pointing to
C:\projects\powershell\src\powershell-win-core\bin\Release\netcoreapp1.0\win81-x64\publish
However on Travis CI test runs, the PSHome path is pointing to the root folder.
/home/travis/build/PowerShell/PowerShell/src/powershell-unix/bin/Linux/netcoreapp1.0/ubuntu.14.04-x64
This means that appveryor runs under ..\publish folder but travisCI runs under one level up.
Are tests supposed to be running under ..\publish folder?
To workaround this problem I have to restore PackageManagement and PowerShellGet modules during build time to publish folder and one level up.
I think the fix should be in start-pspester.
Steps to reproduce
Add $PSHome $env:PSModulePath to one of your checkin test and watch the output
Expected behavior
Tests are supposed to be running under ..\publish folder
Actual behavior
Described above.
Environment data
Alpha.12