Hi Florent,
Well done! I note there are two kinds of scenarios for XSpec, either using Ant or using XProc. I guess XProc test harnesses are going to be the prefered and most maintained way of launching running XSpec test suites (IMHO the only "raison d'etre" of the Ant way is for systems without an XProc processor).
As we discussed at XML Prague, the main reason we went for ANT in favor of XProc was the ability to pass extensions libraries to the processor. Currently the only way you can do that for an XProc transformation is to edit an XML descriptor and put the jars in Oxygen lib. So we lack the dynamic configuration of the extensions. But the good news is that we intend to extend the XProc scenario to be able to specify the extension libraries that will be automatically loaded. As soon as we add this functionality we will be able to make the XProc scenario the default one.
But it looks to me like the XProc scenario is too closely related to the Saxon test harness. Currently we focused on the XSLT part and since Saxon is the only engine supported by XSpec, these are the default scenarios we added. The next version we will focus on the XQuery part.
In addition, it would be very interesting to be able to configure some of the standard harnesses with details that come from oXygen's data sources. That's a good idea! We did something similar for XSLT: if you generate an XSpec for an XSL with an associated transformation scenario, we take the Saxon configuration from the scenario and we create a custom XSpec scenario that will run with the same Saxon configuration (and the same the extensions). We will probably do the same for XQuery: we will detect the data source from the transformation scenario and we will use the proper harness (eXist, ML etc) configured as in that data source.
Best regards, Alex -- Alex Jitianu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 5/23/2012 7:57 PM, Florent Georges wrote:
George Cristian Bina wrote:
Hi,
We are happy to announce that version 14 of oXygen XML Editor is almost ready for release. Because the new version introduces many new features, we decided to release this beta version and thus have the chance to receive your early feedback before the final release. Thanks for sharing this beta!
*XSLT Unit Test* oXygen 14 comes with XSpec to provide XSLT Unit Test support. That's good news!
a default transformation scenario is set on XSpec files which run the tests, generating as output the test report, so all you need to do to run your tests is to click on the "Apply transformation" button. Well done! I note there are two kinds of scenarios for XSpec, either using Ant or using XProc. I guess XProc test harnesses are going to be the prefered and most maintained way of launching running XSpec test suites (IMHO the only "raison d'etre" of the Ant way is for systems without an XProc processor). But it looks to me like the XProc scenario is too closely related to the Saxon test harness. I guess the ideal situation would be to have radio buttons to select between the standard harnesses AND a file input if the user wants to provide his/her own pipeline harness.
In addition, it would be very interesting to be able to configure some of the standard harnesses with details that come from oXygen's data sources. It would be very handy for a user to say: "I want to run this test suite on this or that data source". E.g. if the data source is an eXist data source, oXygen already knows all the details to pass to the XProc test harness, like the connection point, etc.
Thank you for this new feature in oXygen!
Regards,
-- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user