XSLT Unit testing

Question

Does anyone know of a way to write unit tests for the XSLT transformation?

I've a lot of XSLT files and it's getting harder to test them manually. We have an example XML and can compare it to the resulting output XML from the XSL transormation. However, I'm looking for a better test method.

score 13 · Answer 1 · answered Jul 26 '12 at 18:25

I am currently looking for some good options to do this as well. As a result, I came across this question, and a few other potential candidate solutions. Admittedly, I haven't tried any of them yet, so I can't speak to their quality, but at least they are some other avenues potentially worthy of researching.

Additionally, I found the following article to be informative in terms of a general methodology for unit testing XSLT.

Unit test XSL transformations

Unfortunately, this task was placed on the backburner at my work shortly after I started looking into it and I have never had a chance to revisit it. — Scott, Sep 04 '14 at 15:57

score 9 · Answer 2 · edited May 20 '20 at 12:46

9

Try XSpec, a testing framework for XSLT. It allows you to write tests declaratively, and test templates and functions.

edited May 20 '20 at 12:46

David

409
3
14

answered Apr 11 '11 at 15:43

James Sulak

31,389
11
53
57

1

How to test a transformation in a particular mode with XSpec? – Árpád Magosányi Jan 18 '16 at 10:48
As of November '21, xspec is the only option that looks to be still actively maintained. – mcwayliffe Nov 17 '21 at 14:46

score 3 · Answer 3 · edited Aug 30 '14 at 13:43

3

Looks like Oxygen editor has Unit Testing available as well. It "provides XSLT Unit Test support based on XSpec".

I haven't tried it myself, but will soon.

edited Aug 30 '14 at 13:43

Andrej Adamenko

1,650
15
31

answered Aug 02 '13 at 06:14

Vadim Peretokin

2,221
3
29
40

Paul Sweatte · Answer 4 · 2017-09-28T23:42:37.090

Here are a few simple solutions:

Use xsltproc with a mock XML file:
```
xsltproc test.xsl mock.xml
```
XSLT Cookbook - Chapter 13

Create a document() placeholder variable and comment/uncomment it manually:

<xsl:variable name="Data" select="descendant-or-self::node()"/>
<!-- 
<xsl:variable name="Data" select="document('foo.xml')" />
-->
<xsl:if test="$Data/pagename='foo'">
  <p>hi</p>
</xsl:if>

Create a condition to swap the comment programmatically:

    <xsl:variable name="Data">
      <xsl:choose>
        <!-- If source XML is inline -->
        <xsl:when test="descendant-or-self::node()/pageName='foo'"/>
         <xsl:value-of select="descendant-or-self::node()"/>
        </xsl:when>
        <!-- If source XML is external -->
        <xsl:otherwise>
         <xsl:value-of select="document('foo.xml')" />
        </xsl:otherwise>
      </xsl:choose>
    </xsl:variable>

Use a shell script to inline the data programmatically in the build to automate the tests completely.

References

score 1 · Answer 5 · answered Dec 16 '13 at 05:35

1

We have been using Java based unit test cases, in which we provide expected xml string after transformation and input xml string which needs to be transformed using some XSL. Refer to following package if you want to explore more.

org.custommonkey.xmlunit.Transform
org.custommonkey.xmlunit.Diff
org.custommonkey.xmlunit.DetailedDiff

answered Dec 16 '13 at 05:35

user1177969

105
8

Works great, however, some source code would be helpful. Also, it looks like xspec files are useless here... old post I know, but still relevant. – 3xCh1_23 Feb 26 '20 at 20:13

score 1 · Answer 6 · answered Jan 23 '16 at 18:25

I´m using this tool: jxsltunit.

The test is defined by an XML file which is then passed to the tool. This is an example of the test configuration:

<xsltTestsuite xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="jxsltunit jxslttestsuite.xsd" xmlns="jxsltunit"
    description="Testsuite Test"
    xml="min-test.xml"
    xslt="min-test.xslt"
    path="pa > ch">
    <xsltTestcase match_number="0">
        <![CDATA[<ch>child 1</ch>]]>
    </xsltTestcase>
    <xsltTestcase match_number="1">
        <![CDATA[<ch>child 2</ch>]]>
    </xsltTestcase>
</xsltTestsuite>

It takes the XML, the XSL and a path in the transformed XML which gets tested. The path can contain a list which elements are identified by their index.

One benefit of this tool is that it can output the results as a junit XML file. This file can be picked up by your Jenkins to show the XLST-tests in your test results. Just add the call to the tool as a build step.

score 1 · Answer 7 · answered Nov 12 '18 at 06:39

Try Jenni Tennison's Unit Testing Package (XSpec), which is a unit test and behaviour-driven development (BDD) framework for XSLT, XQuery, and Schematron. It is based on the Spec framework of RSpec, which is a BDD framework for Ruby.

With XSpec you can test XLT template wise or XPath wise per your need. For an overview on how to use/handle/write (installation|execution) click https://github.com/xspec/xspec/wiki/What-is-XSpec

XSLT Unit testing

7 Answers7