Fluent Assertions 8.7.0 is here, and it\u2019s a meaningful step forward for teams testing JSON APIs and deep object graphs. This release brings first-class System.Text.Json support<\/strong>, upgrades to BeEquivalentTo precision<\/strong>, and a new way to validate exception messages<\/strong>. The net effect: fewer brittle diffs, more resilient test suites, and clearer intent in your specs.<\/p>\n\n\n\n JSON payloads are now first-class citizens in your tests.<\/p>\n\n\n\n Helpers like BeString, BeNumeric, BeBool, BeUtcDate, and BeAnArray make intent obvious at a glance. If casing differs, use IgnoringJsonPropertyCasing().<\/p>\n\n\n\n BeEquivalentTo gets more precise, giving you surgical control over equivalence checks.<\/p>\n\n\n\nWhy it matters<\/strong><\/h2>\n\n\n\n
\n
JSON support<\/h3>\n\n\n\n
var node = JsonNode.Parse(\"{ \\\"name\\\": \\\"Product\\\", \\\"price\\\": 99.99 }\");\n\nnode.Should().BeEquivalentTo(new { name = \"Product\", price = 99.99 });\nnode.Should().HaveProperty(\"name\").Which.ToString().Should().Be(\"Product\");\nnode.Should().NotHaveProperty(\"code\");\n\nJsonArray array = JsonNode.Parse(\"[1, 2, 3]\")!.AsArray();\narray.Should().NotBeEmpty();<\/code><\/pre>\n\n\n\nObject graph equivalence upgrades<\/h3>\n\n\n\n
\n
\n