Johan Ljunggren

> We're unable block -NotMandatory -Mandatory now due to how Should works Would it work saying `Should -HaveParameter -Mandatory:$false` 🤔

I am not expecting nor need `-CodeCoverage` to work as it is a legacy parameter. I’m talking about `[PesterConfiguration]` object in the issue above.

In our modules we test the built modules (built using the Sampler-project), so we have one big .psm1 file. During development of, for example a function, I want to run...

I have updated the issue for the Pester 5.1.1 where the issue still exist. It is also not possible to use `ActualValue`. ```powershell Describe 'Get-HashTable' { Context 'When returning a...

It is not possible to use `$getHashTableResult.Keys` either. ```powershell Describe 'Get-HashTable' { Context 'When returning a hashtable' { It 'Test' { $getHashTableResult = @{ Property1 = '1' Property2 = '3'...

I good with closing this issue. If `Should -ActualValue $getHashTableResult.Keys -HaveCount 2` should work then we can open up a separate issue for that. Let see what @nohwnd thinks.

`InParameterSet` would work too, didn't think of looking at it from that angle. Then this should work too and is also intuitive: ``` (Get-Command abc123) | Should -Not -HaveParameter 'MyParameter'...

I like `-Throw` and `-Throw -Because` for a custom message. But then it would also be great if we could output the command name, e.g. if we have `-Throw -Because...

Great discussions here, I label this as help wanted and resource proposal so that someone in the community can grab this a run with it! Looking forward to one or...

Yes it is still outstanding. There has been no resource(s) added to this module for that purpose. The community need to send in a PR that add this.