We do this by putting the login (same for logout) into a module, and include it into the scripts with !ENTITY, eg. <!ENTITY loginPlanAdmin SYSTEM "file:../modules/loginPlanAdmin.xml">
then where we want to invoke this we use: &loginPlanAdmin; This is pretty old-school, I think there's a newer and better way. But we use 'modules' for all code that is used in more than one script, for ease of maintenance. -- Lisa On Fri, Oct 17, 2008 at 5:07 PM, av8r <[EMAIL PROTECTED]> wrote: > > > Hi, > > Currently the way I have my tests written, each one has to invoke the > url to login screen at the beginning of the test, and logout when the > test has finished? > > I have tried to isolate the login and logout to separate tests, but it > does not work. There is no session maintained after I move from the login > test to the actual functional test. > > Is there anyway to maintain the session, so I can eliminate the overhead > of logging in and logging out for each test. > > Thanks, > --H > -- > View this message in context: > http://www.nabble.com/Isolating-login-and-logout-tp20042365p20042365.html > Sent from the WebTest mailing list archive at Nabble.com. > > _______________________________________________ > WebTest mailing list > WebTest@lists.canoo.com > http://lists.canoo.com/mailman/listinfo/webtest > -- Lisa Crispin Co-author with Janet Gregory, _Agile Testing: A Practical Guide for Testers and Agile Teams_ (Addison-Wesley 2009) http://www.agiletester.ca http://lisa.crispin.home.att.net http://lisacrispin.blogspot.com
