Running pester tests from within VSCode using run tests fails with error of no module loaded

[techthoughts2]

Expected Behavior

Sample tests generated by Catesta should be able to be run using Run tests | Debug tests from within VSCode.

Current Behavior

Sample tests generated by Catesta fail when run using Run tests | Debug tests from within VSCode with the following error:

System.Management.Automation.RuntimeException: No modules named 'GHATest' are currently loaded.

Possible Solution

Recent Pester 5 changes in #91 likely introduced a regression with the move of scaffolding to BeforeAll block.

Steps to Reproduce

1. Create a new module with Catesta
2. Try to run sample pester tests from within VSCode using Run tests | Debug tests