Re: mathml 3 tests results

Hello Dani,

I'm moving this thread to the www-math mailing-list as, I think, more people may enjoy such a hint: how to create my own test suite results.

Le 4 avr. 2014 à 12:16, Daniel Marques <dani@wiris.com> a écrit :
> Is there the possibility to run the test at
> "http://i2geo.net/mml-testsuite/mathml3/" offline or installed in our
> internal servers? Or maybe edit the XML by ourselves? 

yes there is but it is not very documented. I used the following trick when I ran the testsuite for wiris at the time, where an applet was displayed for each.

We're running:
	http://www.w3.org/Math/testsuite/run.sh
to build the test suite from source files that are in:
	http://www.w3.org/Math/testsuite/testsuite/ (can't list files)

The run.sh uses mostly run.jelly, a fairly old xml-pipeline scripting engine (http://commons.apache.org/proper/commons-jelly/) that is perfect for that task. That thing, in turn, processes each of the xml files (list here: http://www.w3.org/Math/testsuite/build/main/toc.xml) producing several output files inside "build", one for each "type of test suite road" (main, mathml3, …) using, for each, an XSLT transformation, from the xml sources.

The XSLT transformed output, for the case of a reported test-output, produces html with forms and javascript that produces a sequence of (~1600) html pages that the user can browse to report the test-suite-results to the server on i2geo. The files are all finished with "-form.xhtml". After you have finished the run of a "road" you would get a URL which I can get, verify, and upload as part of the general test results (http://www.w3.org/Math/testsuite/results/tests.html).

For testing the Wiris OpenMath editor, or any other, you would do the following:
- ask us to give you a zip of all the files (this will include a jelly shell script and a fatJelly.jar)
- modify the XLST file w3c.xsl
- invoke run.sh to produce the build that contains your representation method (e.g., to create applet code, or to create a pdf embedder) 
- run the built test suite (typically you take a directory under build and put jt somewhere web-accessible), it should let your browser communicate directly with the server on i2geo.net
- At the end (or when you stop) the test-run, it should offer you a link to an XML file that represents the table of contents annotated with your results. It may be unreadable from you. 

That URL js what we need to pull, verify, and upload so as to incorporate it in the test suite results display.

Paul