If you compare the ECMAScript datamodel XSLT generator with the XPath datamodel xslt generator, it looks like the XPath generator might have been used to compile this test:
XPath:
<xsl:template match="//@conf:systemVarExpr">
<xsl:attribute name="expr">
$
<xsl:value-of select="."/>
</xsl:attribute>
</xsl:template>
ECMAScript:
<xsl:template match="//@conf:systemVarExpr">
<xsl:attribute name="expr">
<xsl:value-of select="."/>
</xsl:attribute>
</xsl:template>
So, I would recommend re-downloading confEcma and using xsltproc to regenerate test321: http://www.w3.org/Voice/2013/scxml-irp/confEcma.xsl
I believe this should remove the ‘$’ variable prefix and give us the proper test.
We may want to run this on other system tests.
I also noticed that there’s a manifest: http://www.w3.org/Voice/2013/scxml-irp/manifest.xml
Rather than checking these tests into the SCXML test framework, we may want to write a script that automates the process of downloading each test, generating SCXML from txml with xsltproc, running the SCXML tests using SCXML test framework, and producing a report. We should create a new Github issue for this.
If you compare the ECMAScript datamodel XSLT generator with the XPath datamodel xslt generator, it looks like the XPath generator might have been used to compile this test:
XPath:
ECMAScript:
So, I would recommend re-downloading confEcma and using xsltproc to regenerate test321: http://www.w3.org/Voice/2013/scxml-irp/confEcma.xsl
I believe this should remove the ‘$’ variable prefix and give us the proper test.
We may want to run this on other system tests.
I also noticed that there’s a manifest: http://www.w3.org/Voice/2013/scxml-irp/manifest.xml
Rather than checking these tests into the SCXML test framework, we may want to write a script that automates the process of downloading each test, generating SCXML from txml with xsltproc, running the SCXML tests using SCXML test framework, and producing a report. We should create a new Github issue for this.