RE: some tests for SCXML

Stefan,
I think that I have fixed the broken links.  Assertion 410 is supposed to point to test 411 (since test 411 covers both assertion 410 and 411.)  Test 202 hasn't been written yet (none of the tests for the DOM event i/o processor have been.) Can you tell me which other links point to the wrong file?

  Thanks,

-          Jim

From: Stefan Radomski [mailto:radomski@tk.informatik.tu-darmstadt.de]
Sent: Wednesday, March 27, 2013 7:51 PM
To: Jim Barnett
Cc: VBWG Public (www-voice@w3.org)
Subject: Re: some tests for SCXML

Hey Jim,

I was about to integrate the tests into Jacob's scxml test framework, but quite a few of the links to tests point to the wrong file or result in a 404:
http://validator.w3.org/checklink?uri=http%3A%2F%2Fwww.w3.org%2FVoice%2F2013%2Fscxml-irp%2F&hide_type=all&depth=&check=Check

Best regards
Stefan

On Mar 18, 2013, at 8:10 PM, Jim Barnett <Jim.Barnett@genesyslab.com<mailto:Jim.Barnett@genesyslab.com>> wrote:


I have posted the tests for sections 3 and 4 of the SCXML spec.  There are about 50 tests overall, and I will add the tests for the remaining sections of the spec over the next few weeks.  The tests are linked from section 6 of this document,  http://www.w3.org/Voice/2013/scxml-irp/ .  The document and the tests should be publicly accessible.

As you will see from looking at section 5.3 of the doc and the tests themselves, they are not written in scxml directly, but in a higher-level notation that abstracts away the data model.  To run a test, you must put it through an XSLT style sheet to concrete scxml with a datamodel that suits your platform, etc.   Section 5.3 links to style sheets that convert to the XPath and ECMAScript datamodels.

There may be errors in the tests or in the document itself.  I have run the tests  through the XPath stylesheet (= data model) on Johan's system, and it passes all of them except 403c.  I haven't tested the ECMAScript stylesheet.

The document also asks for people to submit their test results.  We don't need that at this point, but we will at a later stage of the W3C process (at which point the document will be officially published.)   There's a lot of boilerplate in the document, most of it copied from another spec, so parts of it may be out of date or irrelevant.

Let me know if you have problems with the doc or the tests.

-          Jim