String difference error broken when ErrorView is ConciseView

[fflaten]

Checklist

• Issue has a meaningful title
• I have searched the existing issues. See all issues
• I have tested using the latest version of Pester. See Installation and update guide.

What is the issue?

In PowerShell 7.1+ the string difference error from Should-BeString, Should -Be/BeExactly is broken using the default ErrorView (ConciseView)

Expected Behavior

A clean and readable error message

Steps To Reproduce

# Same error with 'abc' | Should -Be 'Two' etc.
PS /workspaces/Pester> 'abc' | Should-BeString 'ab'
InvalidResult: 
Line |
   1 | 'abc' | Should-BeString 'ab'
     | Expected strings to be the same, but they were different. Expected length: 2 Actual length:   3 Strings differ at index 2. Expected: 'ab' But was:  'abc'       
     | --^

# Expected
PS /workspaces/Pester> $ErrorView = 'NormalView'                                         
PS /workspaces/Pester> 'abc' | Should-BeString 'ab'
Expected strings to be the same, but they were different.
Expected length: 2
Actual length:   3
Strings differ at index 2.
Expected: 'ab'
But was:  'abc'
          --^
At /workspaces/Pester/src/functions/assert/Common/Invoke-AssertionFailed.ps1:58 char:9
+         throw $errorRecord
+         ~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidResult: (System.Collections.…ring,System.Object]:Dictionary`2) [], Exception
+ FullyQualifiedErrorId : PesterAssertionFailed

Describe your environment

Pester version : 6.1.0-alpha2 /workspaces/Pester/bin/Pester.psm1
PowerShell version : 7.6.2
OS version : Unix 6.18.35.2

Possible Solution?

ConciseView trims newlines, so maybe fallback to simple Should-Be error like Expected [string] 'ab', but got [string] 'abc'.?

Override $ErrorView to NormalView if ConciseView?

[fflaten]

Side note: Should the caret point at the last matching character or the first difference? Classic vs new assertions behave different

# 'abc' | Should-BeString 'ab'
Expected: 'ab'
But was:  'abc'
          --^
# 'abc | Should -Be 'ab'
Expected: 'ab'
But was:  'abc'
           --^

Intended change or bug/inconsistency?

[nohwnd]

I though we disable the concise view for any assertion error exactly because of this problem.

The location difference is weird, we probably should point at the difference, not at the last same character, but should be consistent. Let's look at how xunit / mstest / nunit do it and then decide (I might have made it buggy in mstest as well :D )

[fflaten]

I though we disable the concise view for any assertion error exactly because of this problem.

We set NormalView in build.ps1 and test.ps1, but no warning, fix or even docs for end users. Bad first impression and UX.

We could maybe adjust the error message if ConciseView and/or provide a first-time warning about "reduced error details" because of it? I believe we have/had a first-time warning somewhere already.