On Thu, Apr 7, 2011 at 8:39 AM, Frank Bennett <[email protected]> wrote:
> On Thu, Apr 7, 2011 at 9:28 PM, Bruce D'Arcus <[email protected]> wrote:
>> On the test suite itself ...
>>
>> On Thu, Apr 7, 2011 at 3:40 AM, Frank Bennett <[email protected]> wrote:
>>
>> ...
>>
>>> The "syntax" of the test fixtures is admittedly a dog's breakfast
>>> currently, set up in a rush before speeding forward with the coding.
>>> JSON has been used to describe the input data mostly because it does
>>> not require conversion (saving me the time required to write a
>>> converter), and because typing hundreds of tests in JSON by hand is at
>>> least a little less painful than writing hundreds of tests in XML.
>>> However, now that we have the processor running in at least two
>>> interactive applications, recasting the fixtures in a single uniform
>>> syntax seems a good idea, and the obvious choice would be XML.
>>
>> Two things:
>>
>> 1) are you suggesting re-casting the JSON input data as well in this
>> context as XML, or simply embedding the JSON in an XML node? I presume
>> the latter.
>
> It could be either. I had the former in mind, but I suppose the latter
> could be a whole lot simpler to code, now that you mention it. Once
> converted from my junkyard file format to something more standard, the
> content could be refactored to taste.
We could start with:
<data type="json"></data>
In any case, what do we need?
<test mode="citation">
<style/>
<data type="json"></data>
<result>
<expected/>
<actual/>
</result>
</test>
That work?
Anything else?
<https://gist.github.com/909764>
Might be cool if the XML test could get fed to cucumber.
Bruce
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
