Conversation
Remove direct import call, since we are leveraging auto-discovery for Pester module
| ) | ||
|
|
||
| & (Get-PSOutput) -noprofile -c "Import-Module '$PSScriptRoot/src/Modules/Pester'; Invoke-Pester $Flags $Directory/$Tests" | ||
| & (Get-PSOutput) -noprofile -c "Invoke-Pester $Flags $Directory/$Tests" |
There was a problem hiding this comment.
Why?
I added this because the Win10 version was getting imported on my Win10 dev machine.
There was a problem hiding this comment.
I moved Pester into src/Modules/Shared, so this call fails as-is. We copy pester into the output, we should import it from there.
There was a problem hiding this comment.
Import-Module : The specified module
'/home/travis/build/PowerShell/PowerShell/src/Modules/Pester' was not loaded
because no valid module file was found in any module directory.
At line:1 char:1
+ Import-Module '/home/travis/build/PowerShell/PowerShell/src/Modules/P ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (/home/travis/bu.../Modules
/Pester:String) [Import-Module], FileNotFoundException
+ FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Comm
ands.ImportModuleCommand
|
Per offline discussion with @lzybkr new proposition:
|
@JamesWTruher we need to try the upstream package again. I know it makes some specific Windows calls, but we could potentially get PowerShell to respond with mock data or something to enable this kind of compatibility. |
4 participants
Remove direct import call, since we are leveraging auto-discovery for Pester module