Pester | ubiquitous test and mock framework | Command Line Interface library

The problem is this line at the start of your function:

One way to do it, is to use SelectSingleNode():

Mathias R. Jessen provided the crucial pointer in a comment - simply omit the inner { and } - but since I've seen the underlying misconception before, it's worth digging deeper:

While { ... } blocks are a regular part of most PowerShell statements, such as foreach and if, in isolation they do not provide a scoped block of statements that are immediately executed, the way it would work in C#, for instance.

Instead, { ... } in isolation is the literal form of a PowerShell script block, i.e. a block of statements for later execution, on demand, either via &, the call operator, for execution in a child scope of, or via ., the dot-sourcing operator, for execution directly in the scope of origin - which may or may not be the caller's scope (see caveat below).

Thus, such a script-block literal must either be saved in a variable or passed to a command expecting a script block in order to be executed later.

Absent that, a script block is implicitly output to the success output stream, which by default goes to the console (host), causing it to be rendered by its .ToString() value, which is simply the verbatim content of the script block, excluding the delimiters ({ and }).

For instance:

This is quite tricky. It looks to me that there are two issues:

1. Your Mock isn't firing because the -ParameterFilter isn't matching the invocation of Get-ADUser.
2. You need your tests to Mock Get-ADUser in 2 different ways, so that when first used it returns a result but when invoked the 2nd time it returns nothing.

I've created what I think is a working solution, but because getting -ParameterFilter to work well with Get-ADUser's -Filter parameter seems to be very difficult, I changed your function so that for one of the Get-ADUser calls it includes the -Properties parameter, so that I could differentiate the use based on that. An alternative approach might be to create two wrapper functions around Get-ADUser for when you use it the first vs 2nd time.

Here's my solution. I also had to edit your function as I was missing the part where you set $BaseSam. This passes for Bruce Wayne but not for Clark Kent as it doesn't handle the foreign characters.

It looks like you're probably using Pester v5. As such your mock needs to be in a BeforeAll or BeforeEach block.

This should work:

You could create a wrapper PowerShell script that determines the tags prior to calling Invoke-Pester and then you can use that to Invoke Pester with the required tags.

For example:

It is the value of $PesterPreference.CodeCoverage.CoveragePercentTarget.Value, i.e the minimum amount of test coverage you want to achieve. This is set to 75% by default.

It's mentioned on the page describing New-PesterConfiguration:

• https://pester-docs.netlify.app/docs/commands/New-PesterConfiguration

CoveragePercentTarget: Target percent of code coverage that you want to achieve, default 75%. Default value: 75

But it was quite hard to figure out, and it could do with being added to the documentation page about test coverage. I ended up searching through the source code and found that the message you listed is output here:

• https://github.com/pester/Pester/blob/1515194f4868f6aaae82d7d376a8a776afe0ebf4/src/functions/Output.ps1

-ForEach is processed during the Discovery-phase, while BeforeAll is processed later during the Run-phase so the solution is to use a foreach loop inside the it block.

As I stated in my comment, this is odd, and should be resolved earlier in the code base. However, if that is not possible, use Invoke-Expression

like so