Closed DennisL68 closed 2 months ago
I first use this: https://github.com/gaelcolas/Sampler/issues/87#issuecomment-2277283023
If the module contain classes or assemblies that are changed between test runs I have a Invoke-PesterJob
that starts Pester in a separate job, that way I can re-build the module and it is not blocked by loaded classes and assemblies. I planning to publish Invoke-PesterJob
to the module Viscalyx.Common eventually.
I suggest adding that above functions to your own module and publish it to PS Gallery.
I merged the my Invoke-PesterJob
in the module Viscalyx.Common.
I hope it helps the community.
Closing this as per comment https://github.com/gaelcolas/Sampler/issues/492#issuecomment-2299025299.
I noticed, when rebuilding my module in iterative stages, that my changes wouldn't be reloaded by PowerShell (for a deeper explanation see PowerShell - Reloading module does not reload submodules)
So I had to resort to restarting my PowerShell console between each build. This got so tedious that I placed the following functions in my $profile script to ease the suffering...
Perhaps these two functions could be added by
Sampler
as an option?