Hi, I'm not sure that it is a good strategy to try to run all tests in the same session. Problems in one test may impact results of others. Nevertheless it's probably possible to extract the cookie value and store it in a file in the first test. The next tests then just need to read this value and set the cookie (I've never tested it).
Marc. Troy McGuire wrote: > > I've been trying to figure out a way to keep the same session for a run > of several tests. Currently, the only way I can get multiple tests to > run is to have each script login. I tried to use <!DOCTYPE.... <!ENTITY > ... to load a "login.xml" to automate the login as a workaround, but > that didn't work for me for some reason. What I would _*really*_ like > is for my initial login test to acquire a session ID and be able to use > that same session ID for the rest of the tests (therefore not needing to > login for each test). Is this possible? Can others out there give me > samples of they/you do it? I tried using <storeCookie> since we do > store the session ID as a cookie, but it doesn't seem to work for me > either (maybe since I'm working with multiple test files?). The current > setup I have is a "build.xml" file that calls the other test files > sequentially. Any information in this area would be a big help. > > Thanks, > > Troy > _______________________________________________ > WebTest mailing list > [email protected] > http://lists.canoo.com/mailman/listinfo/webtest > > -- View this message in context: http://www.nabble.com/Maintaining-Sessions-tf2339836.html#a6521279 Sent from the WebTest mailing list archive at Nabble.com. _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
