Return-Path: 
 <commons-dev-return-24806-qmlist-jakarta-archive-commons-dev=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@apache.org
Received: (qmail 60855 invoked from network); 7 Feb 2003 11:32:46 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 7 Feb 2003 11:32:46 -0000
Received: (qmail 29768 invoked by uid 97); 7 Feb 2003 11:34:13 -0000
Delivered-To: qmlist-jakarta-archive-commons-dev@nagoya.betaversion.org
Received: (qmail 29761 invoked from network); 7 Feb 2003 11:34:12 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 7 Feb 2003 11:34:12 -0000
Received: (qmail 60690 invoked by uid 500); 7 Feb 2003 11:32:44 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 60679 invoked from network); 7 Feb 2003 11:32:44 -0000
Received: from carbon.btinternet.com (194.73.73.92)
  by daedalus.apache.org with SMTP; 7 Feb 2003 11:32:44 -0000
Received: from host217-35-21-181.in-addr.btopenworld.com ([217.35.21.181]
 helo=dallaway.com)
	by carbon.btinternet.com with esmtp (Exim 3.22 #23)
	id 18h6kM-0001Ko-00
	for commons-dev@jakarta.apache.org; Fri, 07 Feb 2003 11:32:42 +0000
Message-ID: <3E439888.1030607@dallaway.com>
Date: Fri, 07 Feb 2003 11:29:12 +0000
From: Richard Dallaway <richard@dallaway.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en, de-de
MIME-Version: 1.0
To: commons-dev@jakarta.apache.org
Subject: [latka] ways to handle common tests
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Does anyone have any ideas on good ways to handle units of common test 
code in Latka?

For example: login to an application.  You may need to have a test user 
log in to an application before running certain tests, and it would be 
good to be able to code this common HTTP request in just one place and 
reuse it across many tests.  E.g.,

<session>
   LOGIN-MAGIC-HERE
   <request>
     ... other tests here
   </request> ....
  </session>

It's hackable (maybe) with a DTD/entity ("&login"), but I'm not 
comfortable with that.  I wondering if there's a mechanism for some kind 
of "include" expression?  Something like: <include file="login.xml"/> 
for the login magic?

Another option might be to call the login magic from a JUnit setUp() 
method, but it seems more natural (to me) to have it in a Latka .xml file.

Any thoughts would be much appreciated
Richard


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