File: apas03.html

package info (click to toggle)
xmlunit 1.6-2
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, bullseye, forky, sid, trixie
  • size: 2,456 kB
  • sloc: java: 11,316; xml: 4,515; makefile: 8; php: 1
file content (47 lines) | stat: -rw-r--r-- 4,614 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>A.3.Changes from XMLUnit 1.2 to 1.3</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="XMLUnit Java User's Guide"><link rel="up" href="apa.html" title="A.Changes"><link rel="prev" href="apas02.html" title="A.2.Changes from XMLUnit 1.1 to 1.2"><link rel="next" href="apas04.html" title="A.4.Changes from XMLUnit 1.3 to 1.4"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">A.3.Changes from XMLUnit 1.2 to 1.3</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apas02.html">Prev</a></td><th width="60%" align="center">A.Changes</th><td width="20%" align="right"><a accesskey="n" href="apas04.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="Changes%201.3"></a>A.3.Changes from XMLUnit 1.2 to 1.3</h3></div></div></div>
      

      <div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Breaking%20Changes%201.3"></a>A.3.1.Breaking Changes</h4></div></div></div>
        

        
      </div>

      <div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="New%20Features%201.3"></a>A.3.2.New Features</h4></div></div></div>
        

        <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
            If XMLUnit doesn't find a matching Element for a control
            Element, it will match it against the first unmatched test
            Element (if there is one) instead of creating
            a <code class="literal">CHILD_NODE_NOT_FOUND</code> Difference.
            There now is a new configuration
            option <code class="literal">compareUnmatched</code> in
            the <code class="literal">XMLUnit</code> class that can be used to
            turn off this behavior - as a result
            two <code class="literal">CHILD_NODE_NOT_FOUND</code> Differences
            (one for the unmatched control Element and one for an
            unmatched test Element) will be created instead of a
            single Difference comparing the two likely unrelated
            nodes.  See <a class="xref" href="ar01s03.html#Comparison%20of%20Unmatched%20Elements" title="3.8.6.Comparison of Unmatched Elements">Section3.8.6, &#8220;Comparison of Unmatched Elements&#8221;</a>.
            <a class="ulink" href="https://sourceforge.net/tracker/?func=detail&amp;aid=2758280&amp;group_id=23187&amp;atid=377768" target="_top">Issue 2758280</a>.
          </li></ul></div>
      </div>

      <div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Bugfixes%201.3"></a>A.3.3.Important Bug Fixes</h4></div></div></div>
        

        <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
            If XMLUnit couldn't match attributes (i.e. it encountered
            a <code class="literal">ATTR_NAME_NOT_FOUND_ID</code> kind of
            difference), the XPath expressions of the node details
            have been random.  <a class="ulink" href="https://sourceforge.net/tracker/index.php?func=detail&amp;aid=2386807&amp;group_id=23187&amp;atid=377768" target="_top">Issue 2386807</a>.
          </li><li class="listitem">
            In some cases XMLUnit matched test nodes to multiple
            control nodes and then created a "missing child"
            difference for remaining test nodes even though they would
            have been valid targets for control node matches as well.
            <a class="ulink" href="https://sourceforge.net/tracker/?func=detail&amp;aid=2807167&amp;group_id=23187&amp;atid=377768" target="_top">Issue 2807167</a>.
          </li></ul></div>
      </div>
    </div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="apas02.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="apa.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="apas04.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">A.2.Changes from XMLUnit 1.1 to 1.2</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">A.4.Changes from XMLUnit 1.3 to 1.4</td></tr></table></div></body></html>