Frode Flaten

Exactly, just checking because I believe we mentioned something about looking into this as "fallback" when making -ModuleName more strict in 5.2. I might take a look at the Should...

Friendly reminder @efie45. Do you still want to attempt this? 🙂

Advanced configuration for CodeCoverage isn't possible in Pester v5 atm. Docs are [currently outdated on this topic](https://github.com/pester/docs/issues/196), but it's mentioned in a few hidden places https://github.com/pester/Pester/blob/f22150b08e0c71bc9213b7f6d20985fbefcc915f/src/Main.ps1#L782-L786 and as a [breaking...

I understood that. The point was, poorly communicated by me, that it's intentionally not supported/implemented yet AFAIK. At least for now. 🙂

You can use `$getHashTableResult.Keys | Should -HaveCount 2` or `$getHashTableResult.GetEnumerator() | Should -HaveCount 2`. A hashtable is considered a single item when passed through the pipeline (and in a foreach-loop),...

@iambic69 No disagreement here, but sometimes there are technical limitations. The problem is that due to the pipeline-behavior in PowerShell which doesn't enumerate hashtables-entries unlike other `ICollection/IEnumerable`-types, then by fixing...

There's a difference between assigning null in a hashtable and directly to the options in a `PesterConfiguration`-object. During casting from hashtable, null-values are ignored in general. Assigning to options in...

Thanks for the report. Pester 5 depend on `System.Management.Automation 6.1.0` for the module dll used in PowerShell 6+, so that's probably the cause. The lowest available version for on nuget...

I'll leave this open for @nohwnd. Pester currently supports PS3 and above except for 6.0.x because of this dependency so if it wasn't intentional then we should fix it. 🙂

Friendly reminder @bryanbcook. Do you still want to implement this? 🙂