From 065462f0b599a3377df2062286b13a6a0fbaef7d Mon Sep 17 00:00:00 2001 From: Dominique Schuppli Date: Wed, 10 Dec 2025 13:52:50 +0100 Subject: [PATCH] Improve `CustomAssert.AreXmlEquivalent` fail message ... so we have a better chance at finding out why one of the tests rely- ing on it is flaky on AppVeyor. --- .../Components.DictionaryAdapter.Tests/CustomAssert.cs | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/src/Castle.Core.Tests/Components.DictionaryAdapter.Tests/CustomAssert.cs b/src/Castle.Core.Tests/Components.DictionaryAdapter.Tests/CustomAssert.cs index 9072798f0e..cbc8deb0f2 100644 --- a/src/Castle.Core.Tests/Components.DictionaryAdapter.Tests/CustomAssert.cs +++ b/src/Castle.Core.Tests/Components.DictionaryAdapter.Tests/CustomAssert.cs @@ -27,7 +27,14 @@ public static void AreXmlEquivalent(XmlElement expected, XmlElement actual) if (expected == null) throw new ArgumentNullException("expected"); if (actual == null) throw new ArgumentNullException("actual"); - Assert.True(Matches(expected, actual)); + if (Matches(expected, actual)) + { + Assert.Pass(); + } + else + { + Assert.Fail("XmlElements are not equivalent.\nExpected: `{0}`\nActual: `{1}`", expected.OuterXml, actual.OuterXml); + } } public static void AreXmlEquivalent(string expected, XmlElement actual)