XSPEC and XSLT issue

Post here questions and problems related to oXygen frameworks/document types.
Costin
Posts: 829
Joined: Mon Dec 05, 2011 6:04 pm

Re: XSPEC and XSLT issue

Post by Costin »

Hello,

The Saxon engine version which comes bundled with oXygen XML v17.0 is 9.6.0.5.

Let us know when you need other information.

Best Regards,
Costin
Costin Sandoi
oXygen XML Editor and Author Support
tsm21
Posts: 25
Joined: Wed Apr 15, 2015 8:27 am

Re: XSPEC and XSLT issue

Post by tsm21 »

Hello,

We have written a test case for xslt file in xspec.xml.
Now we want to create a test case report (excel sheet) based on the xspec file.

for example we want to generate a test report based on the <x:param>, <x:scenario>, <x:context>, <x:expect>
from xspec file.

Is it possible to create a test report excel sheet through an xsl file?
If yes then does the oxygen editor have any default xslt file?

Thanks in advance.




Thank you
Sai
tsm21
Posts: 25
Joined: Wed Apr 15, 2015 8:27 am

Re: XSPEC and XSLT issue

Post by tsm21 »

Hello,

Previously We have got a reply from that it not possible to run all the xspec test cases simultaneously due to limitations.
Hello,

There are several solutions/answers but each one has some limitations:

1. From the project view select all the xspec files that you want to run. Right click to display the contextual menu and select the 'Apply Transformation Scenarios' action from the 'Transform' menu. In this way, you will run all the test cases from the selected xspec files. The disadvantage of this solution is that an HTML report is created for each XSpec file.

2. You can use the XSpec's 'import' directive to import the test scenarios from other XSpec files. All the unshared scenarios in that imported XSpec will be run on the stylesheet that this XSpec document describes.

So, you can create a new XSPEC file(driver) which imports multiple XSPec files. Something like this:
> <x:description xmlns:x="http://www.jenitennison.com/xslt/xspec"
> stylesheet="escape-for-regex.xsl"
> xmlns:functx="http://www.functx.com">
> <x:import href="escape-for-regex.xspec"/>
> <x:import href="escape-for-regex2.xspec"/> </x:description>

This solution has the limitation that there is only a single stylesheet that you can test.

Unfortunately, there is no solution to run multiple XSpec files that testes various XSLT files and to produce a single report. This is a feature that is already recorded on the XSpec project used by oXygen, see Create a test suite for XSpec implems (https://github.com/expath/xspec/issues/16).

Regards,
Radu
But we have found out that we can run xspec test cases through java (jxsl).
pls refer the below link.
http://www.balisage.net/Proceedings/vol ... ier01.html

Does the oxygen xml editor support this kind of environment?
If yes? could you please help us to set up the environment.


Thank you
Sai
alex_jitianu
Posts: 1008
Joined: Wed Nov 16, 2005 11:11 am

Re: XSPEC and XSLT issue

Post by alex_jitianu »

Hello Sai,

The JXSL test framework is built on top of JUNIT and it's written in the Java programming language. Oxygen is also written in Java so the two should get along well. I suggest you build an Workspace Access plugin. This plugin will use JXSL to run XSpec test cases. For example the plugin could contribute an action on the toolbar. When the user invokes the action a dialog will be presented in which he can browse for the XSPec files to execute or whatever you decide he should do. We have a sample Workspace Access implementation that can be used as a starting point. After creating the sample SDK project (which is Maven-based), please focus on the oxygen-sample-workspace-access project.

I've tried to install the JXSL project myself but it didn't go as smoothly as I hopped. The pom.xml has a lot of dependencies without a version, Saxon has to be deployed as an artifact (see pom.xml notes). After you solve all these problems, running a mvn install should give you a a jxsl-0.1.12-SNAPSHOT.jar. This jar, together with junit.jar and possibly a few others must be put into the Workspace Access plugin (see the library tag from plugin.xml). From the Balisaje link and the Google code project documentation it looks like the class com.servicelibre.jxsl.scenario.test.xspec.XspecScenarioJUnitTest is the entry point.
Post Reply