Files
PSProxmoxVE/tests/PSProxmoxVE.Tests/_TestHelper.ps1
T
Clint Branham 7962a549f0 fix(test): load module via .psd1 manifest instead of raw DLL
Loading via the module manifest (.psd1) ensures PowerShell sets up
proper assembly resolution context. Loading via raw DLL path bypasses
PS's module loading infrastructure and fails on CI runners where the
.NET SDK's assembly resolution conflicts with PS's bundled runtime.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-19 08:45:23 -05:00

52 lines
1.8 KiB
PowerShell

<#
.SYNOPSIS
Shared module-loading helper for Pester tests.
Dot-source this file inside BeforeAll to import PSProxmoxVE reliably
in both local-dev and CI environments.
#>
# If the module is already loaded, nothing to do.
if (Get-Module -Name PSProxmoxVE) { return }
# 1. Try importing by module name (works in CI where the module is
# installed to a PSModulePath location via dotnet publish + copy).
$available = Get-Module PSProxmoxVE -ListAvailable -ErrorAction SilentlyContinue
if ($available) {
Import-Module PSProxmoxVE -Force -ErrorAction Stop
return
}
# 2. Discover the module manifest (.psd1) from the local source tree.
# Loading via manifest ensures PS handles assembly resolution correctly.
# Prefer the framework that matches the running PowerShell edition.
$repoRoot = Resolve-Path (Join-Path $PSScriptRoot '../..')
$moduleRoot = Join-Path $repoRoot 'src/PSProxmoxVE'
if ($PSVersionTable.PSEdition -eq 'Core') {
$frameworks = @('net9.0', 'net48')
}
else {
$frameworks = @('net48', 'net9.0')
}
$searchPaths = foreach ($fw in $frameworks) {
# Publish output (has all dependencies co-located)
Join-Path $repoRoot "publish/$fw/PSProxmoxVE.psd1"
# Build output
Join-Path $moduleRoot "bin/Debug/$fw/PSProxmoxVE.psd1"
Join-Path $moduleRoot "bin/Release/$fw/PSProxmoxVE.psd1"
}
$moduleManifest = $searchPaths | Where-Object { Test-Path $_ } | Select-Object -First 1
if ($null -eq $moduleManifest) {
throw "PSProxmoxVE module not found. Build the project before running Pester tests."
}
# Remove deps.json if present — it causes assembly resolution conflicts
# when loading a binary module inside PowerShell's own .NET runtime.
$depsJson = Join-Path (Split-Path $moduleManifest) 'PSProxmoxVE.deps.json'
if (Test-Path $depsJson) { Remove-Item $depsJson -Force }
Import-Module $moduleManifest -Force -ErrorAction Stop