[Webtest] Failling to check an email

Tue, 13 Nov 2007 17:50:39 +0100

This is a multi-part message in MIME format.
--------------000107050005060001040704
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Thank you,

After hours spent on trying to configure a debug workbench with Eclipse, 
i'm closer to the
answer that i've ever been. But now, i lack some webtest's internal 
stuff knowledge to get rid of
my issue.

Everything seems to be OK since i reach the filterContent method in the 
EmailMessageContentFilter class.
I run into the defineAsCurrentResponse and reach the ContextHelper 
class. There, I arrive in this method :

public static void defineAsCurrentResponse(final Context context, final 
byte[] responseBytes,
final String contentType, final String urlStr) {
        final WebClient webClient = context.getWebClient();
        final WebConnection originalConnection = 
webClient.getWebConnection();
        try {
            final MockWebConnection mockConnection = new 
MockWebConnection(webClient);
            webClient.setWebConnection(mockConnection);
            mockConnection.setDefaultResponse(responseBytes, 200, "ok", 
contentType);

            // htmlUnit does't currently follow the "current window"
            // check that our faked content will be loaded in what 
WebTest considers as the "current window"
            // cf WT-293
            final WebWindow currentTopWindow = 
context.getCurrentResponse().getEnclosingWindow().getTopWindow();
            // with the <previousResponse/> it may happen that the 
window is not registerd anymore
            if (webClient.getWebWindows().contains(currentTopWindow))
            {
                webClient.setCurrentWindow(currentTopWindow);
            }

            final URL url = UrlBoundary.tryCreateUrl(urlStr);
            HtmlUnitBoundary.tryGetPage(url, webClient);
        }
        finally {
            // remove special connection
            webClient.setWebConnection(originalConnection);
        }
    }

The webClient variable seems to be OK, and the mockConnection works well 
(they reference each other). The default response
of the mockConnection is well set and responseBytes contains my email's 
text (that is the most important things to me).
The only thing that seems to behave badly is that the 
currentWebClientContext of the context variable  has fPreviousResponse 
and fCurrentResponse set both to null.

When the I reach the line final WebWindow currentTopWindow = 
context.getCurrentResponse().getEnclosingWindow().getTopWindow();, 
getCurrentResponse() returns null and that leads to
an exception when "context.null" is called.

So i see what happens during the execution, but I don't know the 
"normal" behaviour of this classes and especially when the responses 
(previous and current) are set and defined. I suppose it could be done 
when connection and webClient register themselves, but I am a webtest 
newcomer (newbie?) and I  can't be sure  of that

If someone knows what happens and could help me, it would be awesome

Thanks

Florent Blondeau

Paul King a écrit :
>
> I'll see if I can have a look shortly.
>
> Paul.
>
> _______________________________________________
> WebTest mailing list
> WebTest@lists.canoo.com
> http://lists.canoo.com/mailman/listinfo/webtest

-- 
Pingwy
27, rue des arènes
49100 Angers

--------------000107050005060001040704
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
 <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thank you, 
 
After hours spent on trying to configure a debug workbench with
Eclipse, i'm closer to the 
answer that i've ever been. But now, i lack some webtest's internal
stuff knowledge to get rid of 
my issue. 
 
Everything seems to be OK since i reach the filterContent method in the
EmailMessageContentFilter class. 
I run into the defineAsCurrentResponse and reach the ContextHelper
class. There, I arrive in this method : 
 
public static void
defineAsCurrentResponse(final Context context, final byte[]
responseBytes, 
final String contentType, final String urlStr) { 
        final WebClient webClient = context.getWebClient(); 
        final WebConnection originalConnection =
webClient.getWebConnection(); 
        try { 
            final MockWebConnection mockConnection = new
MockWebConnection(webClient); 
            webClient.setWebConnection(mockConnection); 
            mockConnection.setDefaultResponse(responseBytes, 200, "ok",
contentType); 
            
            // htmlUnit does't currently follow the "current window" 
            // check that our faked content will be loaded in what
WebTest considers as the "current window" 
            // cf WT-293 
            final WebWindow currentTopWindow =
context.getCurrentResponse().getEnclosingWindow().getTopWindow(); 
            // with the &lt;previousResponse/&gt; it may happen that
the window is not registerd anymore 
            if (webClient.getWebWindows().contains(currentTopWindow)) 
            { 
                webClient.setCurrentWindow(currentTopWindow); 
            } 
            
            final URL url = UrlBoundary.tryCreateUrl(urlStr); 
            HtmlUnitBoundary.tryGetPage(url, webClient); 
        } 
        finally { 
            // remove special connection 
            webClient.setWebConnection(originalConnection); 
        } 
    } 
 

The webClient variable seems to be OK, and the mockConnection works
well (they reference each other). The default response 
of the mockConnection is well set and responseBytes contains my email's
text (that is the most important things to me). 
The only thing that seems to behave badly is that the
currentWebClientContext of the context variable  has fPreviousResponse
and fCurrentResponse set both to null. 

When the I reach the line final
WebWindow currentTopWindow =
context.getCurrentResponse().getEnclosingWindow().getTopWindow();,
<big><big>getCurrentResponse() returns null</big></big><big><big> and
that leads to 
an exception when "context.null" is called. 
</big></big>
<big><big>So i see what happens during the execution,
but I don't know the "normal" behaviour of this classes and especially
when the responses (previous and current) are set and defined. I
suppose it could be done when connection and webClient register
themselves, but I am a webtest newcomer (newbie?) and I  can't be sure 
of that 
</big></big>
<big><big>If someone knows what happens and could help
me, it would be awesome 
</big></big>
<big><big>Thanks</big></big>
<big><big>Florent Blondeau 
</big></big>
 
Paul King a écrit :
<blockquote cite="mid:4738AC6F.8060506@asert.com.au" type="cite"> 
I'll see if I can have a look shortly.
 
 
Paul.
 
 
_______________________________________________
 
WebTest mailing list
 
<a class="moz-txt-link-abbreviated" href="mailto:WebTest@lists.canoo.com">WebTest@lists.canoo.com</a>
 
<a class="moz-txt-link-freetext" href="http://lists.canoo.com/mailman/listinfo/webtest">http://lists.canoo.com/mailman/listinfo/webtest</a>
 
</blockquote>
 
 
<pre class="moz-signature" cols="72">-- 
Pingwy
27, rue des arènes
49100 Angers
</pre>
</body>
</html>

--------------000107050005060001040704--