Johan Ljunggren

I got it to not report the error using this code, though not sure this will work since Validate doesn't do anything. Not sure if it needs to do anything....

I don't think this one can be resolved? I thought I share my findings if someone else stumbles on the same problem, or if there are someone that can figure...

It wouldn't be as clean, but I think it is better than how it works today (since it does not work at all today). 🙂 Would it be hard to...

The root cause is that we cannot have parameter sets in the current `Should` so we can add parameters that are intuitive 🤔 What I understood by comments in other...

I just tried this in a test of mine, and it seems to work pretty well. Is there any downside to this? ``` It 'Should call the mock with the...

Hope this helps. We have the paths 5 folders down, and we point from where should start looking for the relative path using [`pathToSources`](https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/test/publish-code-coverage-results?view=azure-devops#arguments). We get the code coverage looking...

I have not seen this impact code coverage upload too tools like CodeCov.io. 🤔 Do you have a xml file that is generated erroneous and what the line should actually...

I'm not seeing this in my tests, though I always have a Context-block that is doing the `ForEach` and always have It-blocks inside Context-blocks. Can you confirm that it outputs...

I refactor unit tests between Pester 4 to Pester 5, and in one instance I by accident saw that one test using `ForEach` did not run any tests. This was...

Works for me to have that as an option in the settings, I would enable it for v5,, and I'm also okay with that it defaults to `$true` in v6.