On 07/04/2008, Randy J. Ray <[EMAIL PROTECTED]> wrote: > All, > > Inspired by a u.p.o journal post that Ovid made ( > http://use.perl.org/~Ovid/journal/36010), I've been working on a module that > will unify testing capabilities for various markup/serialization formats. > Right now, I plan on: > > * XML validity against a DTD > * XML validity against a XML schema > * XML validity against a RelaxNG schema > * YAML validity > * JSON validity > * Content testing via some combo of Test::Deep and/or built-in capabilities > from Test::JSON et al
I would say put as much as possible of this outside the Test:: namespace and then wrap in a thin Test:: wrapper. I wish I'd done this with Test::Deep, it's on the todo list but I'll never get around to it, F > This is based mostly from Ovid's post, but also from the realization that > for these. most of the desired kinds of tests are the same: Does it parse? > Is it valid against the spec? Is the content what I was expecting (allowing > for acceptable variations in textual format)? > > One thing I would like advice on (besides suggestions for future features), > is, errr, the name. Right now, I'm leaning towards Test::Markup. That might > wind up the YAML guys a bit, though (which is actually a quite-acceptable > bonus to me), possibly the JSON camp as well. So I am also considering > Test::Serialization, since all of these amount to forms of serialization. > Even (some would say *especially*) XML. > > Randy > > -- > Randy J. Ray / [EMAIL PROTECTED] > Silicon Valley Scale Modelers: http://www.svsm.org > Sunnyvale, CA >
