commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kurt Schrader <>
Subject Re: [latka] ways to handle common tests
Date Fri, 07 Feb 2003 18:37:22 GMT
I write my Latka tests as Jelly file and then run them in order using
somthing like this:

<j:jelly xmlns:j="jelly:core">
  <j:include uri="RegisterStudent.jelly"/>
  <j:include uri="ApproveRegistrantTest.jelly"/>
  <j:include uri="DeleteRegistrantTest.jelly"/>

I'm assuming that something like that would work for what you want to do.


On Fri, 7 Feb 2003, Richard Dallaway wrote:

> 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>
>    <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:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message