Re: Missing SCXML Test Coverage

I've updated test354 and added test288, which tests that you can assign 
via inline content.  I've changed my mind about adding a companion test 
to test487, though, because I think it's  impossible to do.  test487 is 
supposed to test that assignment of an illegal value  to a location in 
the datamodel results in an error.  But I don't think that there's much 
of anything that we can specify inline that would  be illegal, since the 
value can always be interpreted as a string.  In fact, test487 doesn't 
really test what it's supposed to, since it doesn't try to assign an 
illegal _value_.  Instead it evaluates an illegal _expression_ and test 
that that causes an error.  (So it's likely that it's the expression 
evaluation that causes the error, not the subsequent assignment.)  But 
I'll leave test487 as it is for the time being, since it's worth testing 
that case anyways.

- Jim
On 7/1/2014 11:32 AM, Gavin Kistner wrote:
> Sounds reasonable to me. Please let us know when these have been 
> added, and I’ll update my converter to match.
>
> On Jul 1, 2014, at 9:28 AM, Jim Barnett <1jhbarnett@gmail.com 
> <mailto:1jhbarnett@gmail.com>> wrote:
>
>> On this point, though, I think you're right.  We should add tests for 
>> <assign> with child  content.  Tests 287 and 487 test <assign> with 
>> 'expr'.  I will add tests 287a and 487a that test with <content>.  
>> Instead of adding <conf:content>, I think I'll add <conf:someVal> 
>> which can be a child of <content>.  Then I'll add 
>> conf:eventDataSomeVal and conf:idSomeVal that test that _event.data 
>> and the specified variable have whatever val was created by 
>> <conf:someVal>. I will use <conf:someVal> in test354 as well.
>>
>> On 6/30/2014 5:16 PM, Gavin Kistner wrote:
>>> One feature that I know that LXSC does not support is not covered in 
>>> the tests:
>>> <assign> elements with child content instead of an expr attribute.
>>> I'm not sure if there are others features not covered by tests.
>>>
>>> Ideally every "must" in the specification would have at least one 
>>> test file backing it.
>>
>> -- 
>> Jim Barnett
>> Genesys
>

-- 
Jim Barnett
Genesys