What is your recommendation about where to specify global configuration

With AssertionOptions.AssertEquivalencyUsing(options => options.IncludingAllRuntimeProperties()); I can specify my global configuration. But where to define it best?

Some static constructor of some random type?

Any advice?

[dennisdoomen]

Yep. That would be my first thought as well. I would welcome a PR or at least a separate issue.

[philippdolder]

Might be a bit late to the party, but I think we now got a solution that works for us (we’re using xUnit.net). From my understanding shared context in xUnit.net doesn’t work, since the AssertionOptions is static, i.e. one shared instance per AppDomain, i.e. broader lifetime than any xUnit shared contexts.

public static class GlobalFluentAssertionsConfiguration
{
    private static readonly object Lock = new object();
    private static bool alreadyLoaded = false;

    public static void Configure()
    {
        lock (Lock)
        {
            if (alreadyLoaded)
            {
                return;
            }

            alreadyLoaded = true;

            AssertionOptions.AssertEquivalencyUsing(
                options => <do your thing>);
        }
    }
}

we’re calling this method from the static ctor of every test that requires the special assertions. Without the check alreadyLoaded we started to have System.InvalidOperationException : Collection was modified; enumeration operation may not execute. caused by BeEquivalentTo().

Of course this can be a bit cumbersome if you have to do that in every unit test class. But that’s the only simple, reliable way I can think of currently, if you’re not into using some kind of magic as @ursenzler chose with Fody