My company has a large body of common tests, and we
declare those tests via a DTD. I don't think it's a
hack, it's just XML. :)
- Morgan
--- Richard Dallaway <[EMAIL PROTECTED]> 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>
> 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:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
=====
Morgan Delagrange
http://jakarta.apache.org/taglibs
http://jakarta.apache.org/commons
http://axion.tigris.org
http://jakarta.apache.org/watchdog
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
