If a content author wants to write a test that says "ensure all xml files in a directory contain a specific xpath and value
XMLFile1: No data that match xpath
XMLFile2: No data that match xpath
XMLFile3: Matches xpath and value
Using just the xmlcontent test, this would incorrectly return true, because no items will be create from XMLFile1 and XMLFile2.
It is possible to write content to perform this using the unix or Windows file test to collect items based on filename, then populate a variable with the filepath from the file items, and then writing a xmlcontent test with the filepath of the xmlcontent populated from the variable mentioned above.
This proposal would allow content authors to write less complex content by just enabling a behavior that creates an item if the filepath portion of the object is populated.
If a content author wants to write a test that says "ensure all xml files in a directory contain a specific xpath and value
XMLFile1: No data that match xpath
XMLFile2: No data that match xpath
XMLFile3: Matches xpath and value
Using just the xmlcontent test, this would incorrectly return true, because no items will be create from XMLFile1 and XMLFile2.
It is possible to write content to perform this using the unix or Windows file test to collect items based on filename, then populate a variable with the filepath from the file items, and then writing a xmlcontent test with the filepath of the xmlcontent populated from the variable mentioned above.
This proposal would allow content authors to write less complex content by just enabling a behavior that creates an item if the filepath portion of the object is populated.