Invoke-Pester fails due to missing HelperFunctions since Pester 5.2.0-beta1

[fawohlsc]

General summary of the issue

Invoke-Pester fails due to missing HelperFunctions since Pester 5.2.0-beta1:

Describe your environment

Pester version : 5.2.0-beta1 C:\Users*username*\Documents\PowerShell\Modules\Pester\5.2.0\Pester.psm1
PowerShell version : 7.1.3
OS version : Microsoft Windows NT 10.0.19042.0

Steps to reproduce

Code shared privately with @nohwnd.

Taken from stack trace:

Expected Behavior

Invoke-Pester to execute tests like it did in 5.2.0-alpha3.

Current Behavior

Invoke-Pester fails with error message shared above.

Possible Solution? (optional)

Currently not upgrading from 5.2.0-alpha3 as a workaround.

[nohwnd]

This seems to happen when running Pester from a module that has .psd1 dependency on other module that imports HelperFunctions via moduleToProcess dependency in their .psd1.

The module is some half-loaded state where we see it in Get-Module but can't invoke in it.

No exported commands seen there:

Binary     7.0.0.0               CimCmdlets                          {Get-CimAssociatedInstance, Get-CimClass, Get-CimInstance, Get-CimSession…}
Script     0.0                   HelperFunctions                     
Manifest   7.0.0.0               Microsoft.PowerShell.Management     {Add-Content, Clear-Content, Clear-Item, Clear-ItemProperty…}

Needs a try catch around the clean up logic. And hopefully a test.

[nohwnd]

https://github.com/PowerShell/PowerShell/blob/658837323599ab1c7a81fe66fcd43f7420e4402b/src/System.Management.Automation/engine/runtime/Operations/MiscOps.cs#L53 This is the source of the error. I guess I can check if the returned object has session state (if that is public on the module type) or just handle that type of exception.