Page History

...

• test_AF000, test_AF001, test_AF002
• test_AW000, test_AW001
• test_AX000
• test_AY000
• test_AZ000

Daffodil Test Suite 'daffodil-test'

This is a larger test suite.

Of 3172 tests, 1866 are skipped either because they are negative tests (which are not being evaluated because diagnostic messages vary so widely), or because they use DFDL features known not to be implemented by IBM DFDL such as dfdl:inputValueCalc and dfdl:outputValueCalc, or hidden groups.

That leaves 1306 tests.

202 tests pass as of 2018-12-10. 

1104 fail as of 2018-12-10

Common Test Failures To Be Resolved

The vast bulk of the failures can be explained by a small number of structural problems with the test suite or test infrastructure:

• daf:error - function obviously not supported by IBM DFDL.
• Many daffodil tests put constructs on global elements that are not allowed on global elements by DFDL.
• Many tests have namespace errors - root elements of infosets are not in the proper namespace.  (commonly this is the ex or http://example.com namespace)
• Missing properties (textBooleanTrueRep/FalseRep being undefined is one)
• Mixing of invalid schema errors in the same test suites with other tests.
  
  • Different defineSchema inside a TDML file are not being isolated - compile errors in one stop all tests in that TDML file from compiling.
  • This is a TDML Runner issue.
• Incorrect property syntax: extraEscapedCharacter="%#WSP*; ..." for example
• Missing properties: textBidi, textPadKind, textTrimKind, escapeSchemeRef, documentFinalTerminatorCanBeMissing, and many others are missing from  test environments.

Incompatibilities

• test_timeFunctions01 - IBM DFDL does not support dfdl:calendarTimeZone="" (empty string, meaning 'no time zone')
  • This is problematic because the default format most tests use has this property defined this way.
  • TBD: Perhaps tests should choose from the normal daffodil default formats, and one designed for compatibility??
• dfdl:calendarPattern contains more than 3 "S" symbols. (Should be a warning? - possible bug in cross-test rig)
• separator and escapeCharacter cannot include the same value - this is tolerated by Daffodil. (Allows a delimiter to be escaped by doubling it.)

Incompatibilities Which May be Daffodil Bugs

• When type is long, int, short or byte, DFDL property 'binaryNumberRep' must not be 'bcd' as this cannot have a negative value. (testBCDCharset01)
  • IBM DFDL insists on signed types not being BCD since it has no way to represent negative values.
• Daffodil tolerates not having emptyValueDelimiterPolicy set, if it can show there is no concept of "empty" for the definition. This is not portable because the rules in DFDL are simpler than this. The property simply is required if terminator is defined. (or initiator), regardless of whether there is any notion of empty for a type.
• truncateSpecifiedLengthString - missing
• trailingSkip - missing
• alignment - missing