Open
Description
Summary of the new feature
The latest release fixed Pester 5 problem matching. This is welcome however it is often not immediately obvious that the issue is due to a failed test since it directly uses the syntax of the test. Initial inspection I often think they are syntax errors until I realize what's going on.
Proposed technical implementation details (optional)
The pester problem message should be what Pester reported the error as along with a prepend (e.g. "Test Failed: Expected $true but got $false" and then the source field should be the name of the test, similar to how PSScriptAnalyzer operates.
