In 6.2 top level code in Pester.BeforeContainer.ps1 runs during discovery only. To reach your tests it has to sit inside BeforeAll, the same rule your test files follow. Wrap a bare Import-Module or it is not there.
#pspester#powershell
A dead worker in a parallel run takes its whole test file with it. Pester 6.2 checks that every file came back and fails the run, naming the one that did not. Before, the suite went green one file short.
#pspester#powershell
A second BeforeAll in the same block threw in 6.1. In 6.2 a block takes as many BeforeAll and AfterAll as you want, setups running in the order you wrote them and teardowns in reverse.
#pspester#powershell
Your Pester.BeforeContainer.ps1 silently not applying? In 6.1 Pester found the repo root from the process working directory, which Set-Location does not change. In 6.2 it starts from where your session is.
#pspester#powershell
Pester 6.2.0 is out. Setup files follow your folders now. Every Pester.BeforeContainer.ps1 from the repo root down to the test file's own folder applies, outermost first, so unit tests and integration tests can each have their own setup. #pspester#powershell
