FsUnit.Xunit : when using result type, on error, actual message is not showing the pretty printing but type info.

Description

When the unit test “should equal” failed, an error message indicates the pretty printing for the Expected but only type info the the Actual one.

Repro steps

1. Add the FsUnit.Xunit

2. add a unit test with : Ok "hello" |> should equal (Ok "world")

Expected behavior

Expected result :

FsUnit.Xunit+MatchException: Exception of type 'FsUnit.Xunit+MatchException' was thrown.
Expected: Equals Ok "world"
Actual:  Equals Ok "hello"

Actual behavior

FsUnit.Xunit+MatchException: Exception of type 'FsUnit.Xunit+MatchException' was thrown.
Expected: Equals Ok "world"
Actual:   was Microsoft.FSharp.Core.FSharpResult`2[System.String,System.Object]
   at FsUnit.Xunit.Assert.That.Static[a](a actual, IMatcher`1 matcher) in /Users/sergey/github/FsUnit/src/FsUnit.Xunit/FsUnit.fs:line 19
   at FsUnitBench.AssertBug.result bug() in C:\gh\UnitTestingBenchmark\FsUnitBench\AssertBug.fs:line 9

Known workarounds

let private pretty x = sprintf "%A" x

let shouldBe (expected:'a) (actual:'a) = 
    if expected <> actual then 
        raise (Xunit.Sdk.EqualException(pretty expected, pretty actual))

Related information

• Operating system
• Branch
• .NET Runtime, CoreCLR or Mono Version
• Performance information, links to performance testing scripts

[CaptnCodr]

Fixed with #155.

[CaptnCodr]

I opened a PR #155 which will fix the “ugly” message. Xunit and MsTest messages were affected.