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...)
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. 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. -- Joe (Typo'ed on my phone.) Car Talk has been advised that the staff opticians, C. F. Eyecare, are now under new management. It's Ike and Zeke Leary, now; Lorraine is gone. ________________________________ From: Mukul Gandhi <[email protected]> Sent: Thursday, May 28, 2026 12:37:38 PM To: [email protected] <[email protected]> Subject: Re: xalan-j xpath 3.1 tests progress Hello Xalan-J team, I've added various more W3C XPath 3.1 test sets, to Xalan-J XSL 3 implementation results. The aggregate results for these is available here, https://github.com/apache/xalan-java/blob/xalan-j_xslt3.0_mvn/src/test/java/org/apache/xalan/tests/w3c/xpath3/result/w3c_xpath3_testsuite_xalan-j_result.xml The skipped tests are not included within total count, which likely shows overall more pass %. I think, that this is necessary for Xalan-J's result for W3C XSLT 3.0 test suite, because all schema aware tests, XSLT 2.0 only tests are considered as skipped and we cannot add them to the total tests. Xalan-J uses the same formula for total pass %, for W3C XPath 3.1 test suite. The intention is not to show Xalan-J's XSL 3 quality as higher than actual. We'll see more accurate pass % for Xalan-J's XSL 3 implementation quality, as we'll put more implementation effort. Many thanks. On Wed, May 27, 2026 at 10:19 PM Mukul Gandhi <[email protected]> wrote: > I've been working on developing Xalan-J W3C XPath 3.1 test suite > driver. Following is progress on this task. > > This is the JUnit class from where to run with Xalan-J the W3C XPath > 3.1 test sets included so far, > https://github.com/apache/xalan-java/blob/xalan-j_xslt3.0_mvn/src/test/java/org/apache/xalan/tests/w3c/xpath3/W3CXPath3Tests.java > > Xalan-J XSL 3 results of these XPath tests are following, > https://github.com/apache/xalan-java/tree/xalan-j_xslt3.0_mvn/src/test/java/org/apache/xalan/tests/w3c/xpath3/result/prod > > Hoping we'll have progress on this activity in days and weeks to come. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
