You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 25, 2018. It is now read-only.
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:
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: