Frode Flaten

When migrating, include necessary adjustments discussed in #1367

Related to #318. That should probably enable some view to indicate if a test in the currentblock failed. No ETA atm.

To clarify, do we want to require `-DefaultValue ` when the `DefaultValueType` is `Expression`? Like this? ```powershell Describe 'd' { It 'i' { function myDefault { 'my\default' } function myFunc...

> * In 5.4 I would like to add diagnostic logging to Should and it's assertions, we could check the message for [ ] and some other problematic `-like` wildcards...

There are slight changes to the error messages from these commands, `, but it was` + a few commas. I don't consider this a breaking change since I hope only...

Support for NUnit3 XML-report is being worked on. That schema includes an output-element for standard output from tests. Would that work for you? You'd simply output it like: ```powershell It...

> If I see correctly, Pester 5.4 was until now not released so file attachment and also output this message is not possible still. I am right? @nohwnd @fflaten ?...

While looking into NUnit3 I made a quick PoC with NUnit3-attachment nodes: ```xml , /workspaces/Pester/Samples/demoTagFilter.tests.ps1:4 ]]> D:\a\1\s\demo.tests.ps1 My Abosolute demo README.md My relative demo. Shouldn't work since it's not rooted,...

> Updates to some of the comment-based help and coverage implementation details for local, Visual Studio, VSCode, and Azure Devops integration would be beneficial. I think this type of guides...

Stumbled into an issue with force-importing manifest module with nested module, https://gist.github.com/fflaten/0df7afe3c2a781e2de29aeb55df0b8ff This causes alias and mock to be placed in old import of a nested module while public function...