|Dmitri Plotnikov||Apr 24, 2002 7:06 am|
|Scott Sanders||Apr 24, 2002 6:33 pm|
|Ivelin Ivanov||Apr 24, 2002 7:20 pm|
|Jeff Turner||Apr 24, 2002 10:23 pm|
|Craig R. McClanahan||Apr 24, 2002 10:25 pm|
|Juozas Baliuka||Apr 24, 2002 11:14 pm|
|di...@multitask.com.au||Apr 25, 2002 12:26 am|
|Ivelin Ivanov||May 15, 2002 8:26 pm|
|Jeff Turner||May 15, 2002 10:57 pm|
|James Strachan||May 16, 2002 12:38 am|
|Ivelin Ivanov||May 16, 2002 6:29 am|
|Morgan Delagrange||May 16, 2002 8:31 am|
|Morgan Delagrange||May 16, 2002 8:41 am|
|Ovidiu Predescu||May 16, 2002 10:38 am|
|Jeff Turner||May 16, 2002 4:21 pm|
|Ivelin Ivanov||May 17, 2002 11:09 am|
|Morgan Delagrange||May 17, 2002 11:17 am|
|Ovidiu Predescu||May 17, 2002 11:26 am|
|Ovidiu Predescu||May 17, 2002 11:32 am|
|James Strachan||Oct 30, 2002 4:16 am|
|Vincent Massol||Oct 30, 2002 4:26 am|
|Janek Bogucki||Oct 30, 2002 6:17 am|
|James Strachan||Oct 30, 2002 7:33 am|
|Morgan Delagrange||Oct 30, 2002 8:54 am|
|Ovidiu Predescu||Oct 30, 2002 12:04 pm|
|di...@multitask.com.au||Oct 30, 2002 3:47 pm|
|Subject:||Re: Latka & Anteater|
|From:||Morgan Delagrange (mdel...@yahoo.com)|
|Date:||May 17, 2002 11:17:28 am|
Which HTTP classes do Anteater use? If it's HTTP Client, session support shouldn't be too tough to add.
--- Ivelin Ivanov <ive...@apache.org> wrote:
Session/cookie support is essential indeed. I assumed it's supported in Anteater.
----- Original Message ----- From: "Jeff Turner" <je...@socialchange.net.au> To: "Jakarta Commons Developers List" <comm...@jakarta.apache.org> Sent: Thursday, May 16, 2002 6:21 PM Subject: Re: Latka & Anteater
On Thu, May 16, 2002 at 10:41:55AM -0500, Morgan
----- Original Message ----- From: "Ivelin Ivanov" <ive...@apache.org>
Thank you for the extensive response.
I am having hard time making a choice, but it
appears that Anteater was
built from scratch based on your experience
with Latka and is therefore a
more viable long term solution.
Nono.. Ovidiu Predescu wrote Anteater, in order to automate Cocoon testing (at least partly). Here is his initial post (2001-09-21) outlining the need, and proposed Ant-based solution:
I pointed Ovidiu to Latka, saying:
"Note that [Latka] doesn't use Ant. I suspect this is actually a good thing. Ant 1.x is not flexible enough to be easily repurposed as a http testing engine" -
.. and how wrong I was ;P Ovidiu coded up Anteater in a remarkably short period of time, and announced an initial version here:
(Full cocoon-dev thread is at
So the point is, Anteater was done in full knowledge of Latka (and Cactus). Ovidiu just wanted to try the Ant approach, and proved rather spectactularly that it's a good one. Anteater is a shining example of successful opportunism, whereas Latka is a shining example of traditional software engineering, crafting a solution to a problem.
I don't know about that... :) I think the differences are greater than they appear; it depends on what your needs are.
I'd try to enumerate which
product is better for what, but it's open to interpretation and personal preference.
Objectivism is overrated ;) I'm sure anything you have to say would be useful for people choosing.
Can latka be used for writing complete test
case scenarios: e.g. login, go
through a product purchase, logout?
I've written tests like that. You can wrap
tests in a "session" tag, which
retains cookies and referers between requests.
You can't tell Latka to fill
out forms or push buttons, but you can set
request parameters and request
headers to simulate that kind of user activity.
Anteater doesn't have a <session> tag yet (it's in the TODO), so can't do this sort of thing.
Do you plan to include an option for JUnit reporting in Anteater similar to Latka's, so that tests can integrated with all other junit tests?
Yes that's planned, and there is already a <formatter> element implemented, but I've never seen it working. Ovidiu might know more.
At some point, Latka will probably come with an Ant task.
__________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com