Skip to content
Stefan Bodewig edited this page Dec 11, 2015 · 5 revisions

XMLUnit 2.x has the following goals

  • create functionally equivalent libraries for Java and .NET with very similar APIs
  • the Java and .NET APIs should be idiomatic
  • don't use static configuration settings as XMLUnit for Java 1.x did
  • create a core library without any external dependencies
  • create optional libraries on top of the core - currently planned:
    • xmlunit-matchers containing Hamcrest matchers
    • net-constraints containing NUnit, actually two of them, one for NUnit 2.x and one for 3.x constraints
    • xmlunit-legacy providing an XMLUnit 1.x compatibility layer which requires JUnit 3
  • provide an optional fluent interface as well as a more traditional programmatic API
  • restrict the functionality to what is needed for testing XML, in particular, drop support for HTML and leave it to other libraries to translate HTML to XML

In addition, look into solving some of the issues and feature requests raised against XMLUnit 1.x that had to be rejected for backwards compatibility reasons, these are collected by the "XMLUnit 1.x feature request" label.