如何用FluentAssertions校验非集合对象的非字段等价性（反射对比）

Great question! You're right that NotBe and NotBeSameAs don't fit your needs here—they either rely on the object's Equals implementation or check reference equality, which isn't what you want when you need field-by-field reflection-based comparison.

The Optimal Approach: NotBeEquivalentTo #

If you're using a reasonably recent version of FluentAssertions (v5.x or later), the NotBeEquivalentTo method is exactly what you're looking for. It's the direct reverse of BeEquivalentTo, and works for all object types (not just collections).

This method uses the same reflection-based field/property comparison logic as BeEquivalentTo:

• It doesn't invoke the object's Equals method
• It checks every field/property (unless you configure it to ignore specific ones)
• It passes the assertion if any field/property differs between the two objects
• It fails the assertion if all fields/properties match exactly

Code Example #

Let's use a simple class without an Equals implementation to demonstrate:

public class User
{
    public string Username { get; set; }
    public int UserId { get; set; }
    // No Equals override
}

// Test case 1: Objects are not equivalent (should pass)
var user1 = new User { Username = "jdoe", UserId = 123 };
var user2 = new User { Username = "asmith", UserId = 123 };

user1.Should().NotBeEquivalentTo(user2); // Passes because Username differs

// Test case 2: Objects are equivalent (should fail)
var user3 = new User { Username = "jdoe", UserId = 123 };
user1.Should().NotBeEquivalentTo(user3); // Fails because all fields match

Customizing the Comparison #

Just like BeEquivalentTo, you can configure NotBeEquivalentTo to ignore specific fields/properties, use custom comparers, etc.:

// Ignore the UserId property when checking equivalence
user1.Should().NotBeEquivalentTo(user2, options => 
    options.IgnoringProperties(x => x.UserId));

Fallback for Older FluentAssertions Versions #

If you're stuck on an older version where NotBeEquivalentTo isn't available for non-collection objects, you can wrap the BeEquivalentTo assertion in a check for a failure exception:

// Not as clean, but works for older versions
Action assertEquivalence = () => user1.Should().BeEquivalentTo(user2);
assertEquivalence.Should().Throw<AssertionFailedException>();

This approach verifies that the objects would fail a BeEquivalentTo check, which achieves the same goal as the direct NotBeEquivalentTo method.

内容的提问来源于stack exchange，提问作者Samer Adra