search

ZUGFeRD / mustangproject

Open Source Java e-Invoicing library, validator and tool (Factur-X/ZUGFeRD, UNCEFACT/CII XRechnung)
http://www.mustangproject.org
Apache License 2.0
228 stars 124 forks source link

Unit Test fails upstream #478

Closed hypfvieh closed 1 month ago

hypfvieh commented 1 month ago

I just noted that the TestLibrary unit test fails:

Failed tests:   testLibraryPushItemAllowances(org.mustangproject.validator.LibraryTest): [XPath "/validation/xml/summary/@status" evaluated to value] expected:<"[]valid"> but was:<"[in]valid">
  testLibraryPushRelativeAllowances(org.mustangproject.validator.LibraryTest): [XPath "/validation/xml/summary/@status" evaluated to value] expected:<"[]valid"> but was:<"[in]valid">
  testLibraryPush(org.mustangproject.validator.LibraryTest): [XPath "/validation/xml/summary/@status" evaluated to value] expected:<"[]valid"> but was:<"[in]valid">
  testLibraryPushAllowances(org.mustangproject.validator.LibraryTest): [XPath "/validation/xml/summary/@status" evaluated to value] expected:<"[]valid"> but was:<"[in]valid">
  testMinimumProfileValidityInvoice(org.mustangproject.validator.LibraryTest): [XPath "count(//error)" evaluated to value] expected:<[0]> but was:<[1]>
  testLibraryPushEdge(org.mustangproject.validator.LibraryTest): [XPath "/validation/xml/summary/@status" evaluated to value] expected:<"[]valid"> but was:<"[in]valid">
  testXRValidation(org.mustangproject.validator.LibraryTest): [XPath "count(//error)" evaluated to value] expected:<[0]> but was:<[2]>
  testOXValidationEdge(org.mustangproject.validator.LibraryTest): [XPath "count(//error)" evaluated to value] expected:<[0]> but was:<[1]>
  testMinimumProfileValidityCreditNote(org.mustangproject.validator.LibraryTest): [XPath "count(//error)" evaluated to value] expected:<[0]> but was:<[1]>
  testLibraryPushCorrection(org.mustangproject.validator.LibraryTest): [XPath "/validation/xml/summary/@status" evaluated to value] expected:<"[]valid"> but was:<"[in]valid">

Tests run: 31, Failures: 10, Errors: 0, Skipped: 0

I wanted to update my PR regarding cleanup of POM and tried to build everything and the test above failed. To ensure my changes are not the cause of this issue, I cloned the current master branch in another directory.

When trying to build that, I get the very same unit test failures like above - so I'm sure it is broken upstream and not broken because of my POM adjustments.

langfr commented 1 month ago

Fixed with PR #482.

jstaerk commented 1 month ago

cool thanks