XMLUnit.NET 2.5.1

this release fixes a serious bug in the difference engine when documents only differ in namespace prefix.

The full list of changes for XMLUnit.NET:

• elements that only differed in namespace prefix resulted in a false
  ELEMENT_TAG_NAME difference when compared.
  Issue #22

XMLUnit.NET 2.5.0

this release upgrades the XSLT used by CommentLessSource to use XSLT 2.0 and adds an option to select the XSLT version.

The full list of changes for XMLUnit.NET

• CommentLessSource, DiffBuilder#IgnoreComments and
  CompareConstraint#IgnoreComments now all use XSLT version 2.0
  stylesheets in order to strip comments. New constructors and methods
  have been added if you need a different version of XSLT (in
  particular if you need 1.0 which used to be the default up to
  XMLUnit 2.4.0).
  Issue similar to xmlunit/#99.

XMLUnit.NET 2.4.0

This release changes DefaultComparisonFormatter in order to simplify creating custom ComparisonFormatters.

The full list of changes for XMLUnit.NET

• made DefaultComparisonFormatter more subclass friendly.
  Issue similar to xmlunit/#93.

XMLUnit.NET 2.3.1

This release adds xml docs to the binary distribution and the nuget package, it doesn't contain any functional changes.

XMLUnit.NET 2.3.0

This release allows the schema used in W3C XML schema validation to be specified as XmlSchema when using the Validator or the corresponding constraints.

The full list of changes for XMLUnit.NET:

• Validator and SchemaValidConstraint now accept using XmlSchema
  instances for the schema when validating instance documents.
  Issue similar to xmlunit/#89.

XMLUnit.NET 2.2.0

With this release ISources created from strings or byte[]s can be
used more than once.

The full list of changes for XMLUnit.NET:

• Input.FromByteArray and Input.FromString now return ISources
  that can be used multiple times.
  Issue similar to xmlunit/#84.

XMLUnit.NET 2.1.1

This release fixes a single bug in the CompareConstraint and ValidationConstraint for NUnit2. If you are not using the NUnit2 constraints, there is no need to upgrade from 2.1.0.

The full list of changes:

• CompareConstraint and ValidationConstraint for NUnit2 threw NullReferenceExceptions when combined with another failing Constraint.
  Issue similar to xmlunit/#81.

XMLUnit.NET 2.1.0

The headline feature of this new release are new NUnit Constraints for XPath assertions.

In addition a few DifferenceEvaluator implementations have been added,
a few bugs have been fixed and smaller improvements been made.

The full list of changes:

• added CompareConstraint.WithNamespaceContext
  port of PR #54 by @cboehme.
• added new implementations inside DifferenceEvaluators for common
  tasks like changing the outcome for specific differences or ignoring
  changes inside the XML prolog.
• new HasXPath constraints that check for the existence of an XPath
  inside of a piece of XML or verify additional assertions on the
  XPath's stringified result.
  Port of corresponding matchers in XMLUnit for Java by @mariusneo.
• DiffBuilder.WithComparisonFormatter now also fully applies to the
  Differences contained within the Diff.
  Issue xmlunit/#55

XMLUnit.NET 2.0.0

After three alpha releases this is the first release of XMLUnit.NET 2.x.

The only change when compared to 2.0.0-alpha-04 is

• implemented DiffBuilder.WithComparisonFormatter mentioned in user
  guide.
  Issue xmlunit/#51

XMLUnit.NET 2.0.0-alpha-04

This is the third alpha release of XMLUnit.NET 2.0.0.

The implementation is considered stable enough for a production release. This is an alpha release as we need more people to try out the API in order to call it final.

Breaking Changes since 2.0.0-alpha-03

• the unused SchemaURI property of Validator has been removed.
• the mapping of IDifferenceEngine.NamespaceContext has been
  inverted from prefix -> URI to URI -> prefix in order to be
  consistent with the same concept in IXPathEngine.

Other Changes since 2.0.0-alpha-03

• Comparison now also contains the XPath of the parent of the
  compared nodes or attributes which is most useful in cases of
  missing nodes/attributes because the XPath on one side is null in
  these cases.
  Issue #48
  ported from PR #50
  by @eguib.