Re: Xalan-J XSL 3 test cases submission

Without revealing what the tests are and the anticipated results, I’m afraid this is of no use whatsoever in helping potential developers/users decide how mature your XSLT processor is or even whether it seems to be going in the right direction. Perhaps they indicate you’re making progress, but I can assure you it’s very easy to get the test cases wrong, especially in the all-important edge conditions.

And there is a throughly developed and publicly available set of some O(10,000) XSLT tests available in the W3C test set, as well as the O(20,000) XPath tests. Results against those tests will be much more meaningful, and indeed developing an XSLT compiler incrementally against selected sections of those tests is a very effective design methodology. 

No-one expects you to pass all tests at first, or even twentieth, go, but for example passing most of the xsl:choose tests is a good indicator that you’ve nailed that (fairly simple) section. Indeed when developing the XSLT compiler for SaxonJS, I started by building the code for xsl:choose compilation and testing against the extant test set, and then built outwards over an already tested ‘core’.

I would seriously recommend you move to running portions of the W3C XSLT test suite, and then reporting those results.

John Lumley

Sent from my iPad

> On 1 Apr 2025, at 17:33, Mukul Gandhi <gandhi.mukul@gmail.com> wrote:
> Hi all,
>   The URL of Xalan-J's proprietary (that includes few W3C XSLT3 tests
> as well), but complying to XSLT3 spec, test suite results are now
> available at following links
> 
> https://xalan.apache.org/xalan-j/xsl3/tests/xalan-j_xsl3_test_suite_result.xml
> 
> https://xalan.apache.org/xalan-j/xsl3/tests/xalan-j_xsl3_test_suite_result.html
> (this is little user friendly to look at)
> 
> Many thanks.
> 
>> On Fri, Mar 28, 2025 at 4:58 PM Michael Kay <mike@saxonica.com> wrote:
>>> I can't see how the test results are useful without the tests...
>>> What would be more useful is to contribute new tests to the XSLT3 or XSLT4 test suites.
>> 
>> I've modified Xalan-J's XSLT3 test results file name, to make it
>> stable across modifications to these file contents. The updated URL
>> for this is https://xalan.apache.org/xalan-j/xsl3/tests/xalan_j_xslt3_test_results.xml,
>> which I hope shall not change.
>> 
>> The code and associated meta-data for these Xalan-J tests are
>> available at https://github.com/apache/xalan-java/tree/xalan-j_xslt3.0_mvn/src/test.
>> 
>> I hope that, myself or perhaps someone else from Xalan-J team might
>> spend time in the coming days or weeks, to convert Xalan-J XSLT3 tests
>> implementation to XSLT3's standard test suite format to contribute to
>> XSLT community group.
>> 
>> I'm really not sure, whether myself or someone else from Xalan-J team
>> might get time in very near future to contribute new tests for XSLT4
>> test suite.
>> 
>> The following two XSLT3 spec features are yet not available within
>> Xalan-J, xsl:mode instruction and fn:transform() function which I
>> think are useful. There are few other in-completeness and
>> in-correctness with respect to XSLT3 spec that Xalan-J's XSLT3
>> implementation has.
> 
> 
> --
> Regards,
> Mukul Gandhi