--- Randy J. Ray [EMAIL PROTECTED] wrote:
Test::Text::Format (generic interface)
Test::Text::Format::XML
Test::Text::Format::YAML
Test::Text::Format::Etcetera
Feels a bit clumsy. I tend to dislike starting out three levels deep
unless
the middle level already exists, and there's no
On Mon, Apr 7, 2008 at 10:14 PM, Fergal Daly [EMAIL PROTECTED] wrote:
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,
I am not sure
On 09/04/2008, Gabor Szabo [EMAIL PROTECTED] wrote:
On Mon, Apr 7, 2008 at 10:14 PM, Fergal Daly [EMAIL PROTECTED] wrote:
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
Hi!
On Wed, Apr 09, 2008 at 02:49:05PM +0100, Fergal Daly wrote:
On 09/04/2008, Gabor Szabo [EMAIL PROTECTED] wrote:
On Mon, Apr 7, 2008 at 10:14 PM, Fergal Daly [EMAIL PROTECTED] wrote:
I would say put as much as possible of this outside the Test::
namespace and then wrap in a thin
On Sun, Apr 6, 2008 at 6:18 PM, Elliot Shank [EMAIL PROTECTED] wrote:
Randy J. Ray wrote:
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
Randy J. Ray wrote:
On Sun, Apr 6, 2008 at 6:18 PM, Elliot Shank [EMAIL PROTECTED] wrote:
Test::Text::Format (generic interface)
Test::Text::Format::XML
Test::Text::Format::YAML
Test::Text::Format::Etcetera
Feels a bit clumsy. I tend to dislike starting out three levels deep unless
the
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:
*
* Randy J. Ray [EMAIL PROTECTED] [2008-04-07 02:00]:
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
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
*
Randy J. Ray wrote:
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
10 matches
Mail list logo