Hi Joseph, On Fri, May 29, 2026 at 11:50 AM Joseph Kesselman via dev <[email protected]> wrote: > > For xalan-test, we separated tests into several buckets and provided ways to > invoke all tests (to measure conformance), only tests we knew we should pass > (to detect regression relative the previous tests), tests we failed that we > felt we should be passing (bug reports not yet resolved or features not yet > implemented), tests that we failed but had accepted as explicit divergences > from the Recommendation, and a few other subsets (language tests, api tests, > Xalan-specific feature tests, extension tests...) >
I think, that this is a very good classification of Xalan-J test types. > If you haven't already done so, you might want to follow a similar pattern. > For most builds regression testing is most important, but full conformance > testing is a good thing to be able to report. I agree. We should try to follow this pattern more closely. Presently, Xalan-J XSL3 test set results (and, also the overall tests summary report), have mention of tests status as pass, fail and skipped numbers. The failed tests indicate that Xalan-J is able to run these tests but Xalan-J result is different than the expected result (which indicates the non conformance with the XSL specs). The skipped tests indicate that, Xalan-J implementation is unable to handle running these tests (various times, due to occurrence of inf loops within code). These Xalan-J results are also non conformance with the spec. There are skipped tests, that also indicate Xalan-J doesn't intend to implement a specific feature like streaming, XSLT 2.0 only tests, XPath 1.0 back-ward compatibility tests. > > Do I understand correctly that you haven't implemented schema-aware/typed > processing? The Xylem processor did manage to shoehorn schema types into DTM > via extensions to the node type field/table, but replacing DTM Iterators with > XCI cursors is what exposed that information for processing. XSLT 3.0 schema-aware processing has been implemented. Currently, that requires Xalan-J XSLT 3.0 implementation to start running with flavor as d2d (i.e, an XML DOM source for an XSL transformation). xsl:import-schema instruction also works, which according to XSLT 3.0 spec is one of the feature that needs to be implemented to say that an XSLT 3.0 processor is schema-aware. Xalan-J XPath 3.1 most of the XPath binary operators (esp, when using XML nodes within XPath expressions) are able to use types provided by an XML Schema. Many thanks. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
