Revise expected/actual recent change before shipping 4.1 #7193
Description
- On command-line, I think this will be considered when running the executable in non-server mode, but won't have effect in server (e.g, via dotnet test). Is that intended?
- When considered on command-line, it can lead to duplicate info. The assertion message itself will already show the expected and actual. Is that also intended?
- On TE, I haven't tested yet but I have no idea how/where they handle it.