XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Testing XML don't use xUnit

On Wed, Apr 10, 2013 at 4:52 PM, Michael Kay <mike@saxonica.com> wrote:
>
>
>
>>> Below if as the result of changes to the structure in the XMLe any of
>>> the elements "some" "path" or "to" change, disappear, become reodered,
>>> or now require predicates to be included, changed or removed that test
>>> will not work. Note the multitude of things that the test is
>>> vulnerable to.
>
> The key think with test assertions is to assert the minimum required for success. If it's necessary for the column heading of a table to be bold, include that in the assertion; if this is incidental and irrelevant, then don't. XPath is quite flexible enough to enable you to assert what's necessary and ignore what isn't; that's it's great strength.
>
> Michael Kay
> Saxonica

Right. But XMLUnit doesn't let you do that because it requires an
absolute path (thank you John) to the node you are testing.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS