Replace usage of $MyInvocation.MyCommand.Path with $PSScriptRoot and cleanup tests as a preparation for Pester v5 #1438
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
Pester v5 won't support
$MyInvocation.MyCommand.Path
in theBeforeAll
block any more (in Pester v5 all code will need to be moved into Pester controlled blocks) because of scoping issues, therefore changing to$PSScriptRoot
and replacing test variables called$directory
with a direct call to it for better readability and easier maintenance.Also cleanup some tests that import the
PSScriptAnalyzerTestHelper.psm1
module only for callingTest-PSEditionCoreCLR
, which is just[bool] $IsCoreClr
. Therefore inlining this expression for better readability and reduced maintenance. This change would be needed for Pester v5 as well because the-Skip
expression is evaluated at discovery time where the module function wouldn't be available.This will not make the repo ready for Pester v5 yet, this is just the necessary cleanup without making breaking changes.
PR Checklist
.cs
,.ps1
and.psm1
files have the correct copyright headerWIP:
to the beginning of the title and remove the prefix when the PR is ready.