[Webtest] [webtest][JIRA] Closed: (WT-125) Unable to logout

Marc Guillemot (JIRA) webtest@lists.canoo.com
Thu, 18 May 2006 22:06:28 +0200 (CEST)

     [ http://webtest-community.canoo.com/jira/browse/WT-125?page=all ]
Marc Guillemot closed WT-125:

    Resolution: Invalid
     Assign To: Marc Guillemot

Closing: No information received

> Unable to logout
> ----------------
>          Key: WT-125
>          URL: http://webtest-community.canoo.com/jira/browse/WT-125
>      Project: WebTest
>         Type: Bug

>     Reporter: Annette Cass
>     Assignee: Marc Guillemot

> This problem is related to Jira issue WT-47 -- and I want to suggest that you reconsider re-opening it.  Because one is not able to logout of a program, you cannot have one test or a string of tests that involve multiple logins. This causes a lot of problems when you want to incorporate running multiple tests right after a build.
> Here is part of internal e-mail I created summarizing what I'm doing and errors I'm getting.
> Any pearls of wisdom? Am trying to logout using the invoke command - and am getting an http 302 error.  One possibility is you can't use invoke with this. Another is that the HTML is lacking some additional syntax (such as ?method=onLogout). Maybe we can redirect it after logout to Duke's home page.    Ummmmm.
> XML step that fails:
> <invoke description="Logout" url="${LogoutUrl}" />
> properties:
> createSiteUrl=/protected/registry.do?method=onCreateSite
> viewSiteUrl=/protected/registry.do?method=onViewSites
> LogoutUrl=/protected/logout.do
> from HTML:
>  writeMenuItem (2,'/registry/protected/logout.do','Logout',false);
> CANOO error
> com.canoo.webtest.engine.StepFailedException: Step[invoke "Logout" (23/24)]: Http error 302, at: page - url=http://granite:8085/registry/protected/logout.do, Step: InvokePage at C:\Webtest\webtest\test\CreateSite.xml:61: with (description="Logout", url="/protected/logout.do", stepType="invoke")

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: