The old test driver uses a mix of ways to invoke tests, since some of it tests the language (with input samples and expected output) and some of it tests our APIs. It also has hooks intended to allow running it against other processors. When we started work on it we were one of the first groups to write an XSLT regression test suite; I think we had one before the recommendation committee did.
I haven't looked at what they've done for 3.1; I don't know how hard it would be to drop that into our framework. NOTE: Our current framework relies on being driven by Ant, and has a lot of ad-hoc code, including using Tidy as a basic HTML parser for serializer-sensitive tests which should be compared semantically rather than byte for byte. It does the job but as part of keeping it portable to other processors (including those written in other languages) it is moderately ugly. Writing a new test driver might be worth considering, but we would need to establish whether and how testing other implementations is still required. It wouldn't be a huge task, probably less than my Maven effort, but doing it right is nontrivial. If you are going to consider a new test driver, you might want to spend some time resolving that, and at least understanding what concerns went into xalan-test so you don't repeat some of the mistakes we made along the way. If we *can* make a portable test suite Someone Else's Problem, pointing them to an unmaintained copy of the old xalan-test, that might let us simplify things substantially. -- 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: Sunday, May 24, 2026 11:29:54 AM To: [email protected] <[email protected]> Subject: xpath 3.1 implementation activity Hello Xalan-J team, Little bit of information, related to Xalan-J xslt3.0 development activity. I'm trying to write few XPath 3.1 test cases, from W3C XPath 3.1 test suite into Xalan-J xslt3.0 development branch. I think ideally, we should have an XSL test driver for these test cases, similar to what we have for XSL test cases that we already have within Xalan-J xslt3.0 development branch. W3C XPath 3.1 test suite's schema is little bit different than, W3C XSLT 3.0 test suite's schema. Due to this, I'm currently writing few of these XSL test cases manually within Xalan-J xslt3.0 repos test area. I'm trying to find Xalan-J XPath 3.1 implementation bugs and unimplemented XPath 3.1 features, that I could possibly solve by this activity. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
