commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Janek Bogucki <...@studylink.com>
Subject Re: [latka][anteater][jelly] possible integration... (was Re: Latka & Anteater)
Date Wed, 30 Oct 2002 14:17:55 GMT
Latka does allow parameterization of tests via preprocessing of the test
suite document. It goes like this

>From test-suite.xml

<suite defaultHost="${DEFAULT_HOST}"
        defaultPort="80"
        label="foo">

then on the command line

    $ latka.sh <test-suite-url> prop:DEFAULT_HOST=foo.example.com

While this topic is up could someone commit my documentation patch for
latka? It's still useful to the current alpha release even though it appears
that Morgan is removing XML parsing support from latka, and replacing it
with Jelly.

http://issues.apache.org/bugzilla/show_bug.cgi?id=13426

-Janek


> From: "James Strachan" <james_strachan@yahoo.co.uk>
> Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
> Date: Wed, 30 Oct 2002 12:17:19 -0000
> To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
> Subject: [latka][anteater][jelly] possible integration... (was Re: Latka &
> Anteater)
> 
>> On Wed, May 15, 2002 at 10:26:47PM -0500, Ivelin Ivanov wrote:
>>> 
>>> Can some of the Latka experts please comment on how Latka compares to
>>> Anteater (which emerged from Cocoon)?
>>> 
>>> http://sourceforge.net/projects/aft/
>> 
>> I've worked on both projects, and like both for different reasons.
>> 
>> Latka pros:
>> - Strong typing via a DTD.
>> - Internally, it's got a very nice delegating-SAX-handler model for
>> adding new elements.
>> - Decent XML reporting.
>> - After all Dion's work, it's docs are rather good.
>> 
>> Latka cons:
>> - A PITA to compile, due to it's many dependencies.  Hopefully that's
>> changed with Maven.
>> - The XML file is a bit hard to comprehend at first, due to the use of
>> &entities;
>> - Inflexible XML syntax (see below for definition of 'flexible':)
>> 
>> 
>> Anteater pros:
>> - It's based on Ant (it's really a bunch of Ant tasks). This makes it
>> wonderfully flexible:
>> - I can parametrize tests, by defining variables like ${host},
>> ${port}, ${debuglevel} as properties, and reuse them throughout the
>> script.


--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message