Frode Flaten

Should I look into this? Thinking that we would extend OutputConfiguration with a new option. If not set, auto-detect. Would also limit ANSI-output to the same ConsoleColor-values for now as...

That's the idea. The plan is similar, but tried to also merge multiple messages to a single `write-host` call so we can fix broken redirection of Information-stream. Btw Pester 5.3...

Not yet. Profiled some PoCs when this issue was created, but haven't had time after. Not sure if the stream redirection is worth the perf cost, tried to find the...

There's nothing stopping you from overwriting it already. It is unsupported but as long as you use a parameter-compatible replacement it should work fine. The internal `SafeCommands`-system is mostly there...

Good suggestion. Parameter set support is lacking in general. Noticed it recently while looking at `-Mandatory` which will pass if the parameter is mandatory in any set, but there's no...

`Mock ... -Throw -Because "we're consistent"` 👍 Should this also work with non-default mocks? Like a direct alternative to `-MockWith { throw 'invalid parameters used'}`?

👍 The command name would be part of static error message. `-Because` usually appends an optional message somewhere in the error message. Ex. > Default mock for Get-Something should never...

It was pester CI, build step on windows_2019. Check a PR :) it's been slower lately, but still a minute ++ we don't need for mostly static dependencies.

The PesterTests-project itself could also be deleted until until someone actually wants to write the tests. Most is probably covered through the PowerShell tests.

`Format-Collection` works as expected, returning `@(@(1,2,3))`. However these lines are unrolling the outer array. ``` function ShouldBeFailureMessage($ActualValue, $ExpectedValue, $Because) { # This looks odd; it's to unroll single-element arrays so...