[Webtest] Failling to check an email

Florent Blondeau Florent Blondeau <fblondeau@pingwy.com>
Wed, 14 Nov 2007 11:51:37 +0100


Thanks for your response,

I didn't know for Ant remote debugging (I should have thought about that).

The steps before filterContent are pretty simple ones. I do these ones :
              emailSetConfig(server:"my.server.fr", type:"pop3", 
password:"mypass", username:"my.user@name.fr", delay:"5")
              emailStoreMessageId(from:"/subject/",property:"email01")
              
emailMessageContentFilter(contentType:"multipart/alternative",messageId:"#{email01}")

The setConfig works well and produce no response, it makes me able to 
connect to my server.
The soreMessageId one works well too. It selects the message I want and 
put an id on it. It produces no response.
The contentFilter receive the good message and retreive the good content 
in responseBytes, but fail when arriving
in the method I pointed because of the "nullity" of currentResponse.

I see there is a mockConnection created to cheat htmlUnit (I think) and 
that give responseBytes as a response. It
is the case actually, the defaultResponse of the mockConnection is 
responseBytes, but it seems as if the webClient didn't
register the defaultResponse as the currentResponse though it registers 
the mockConnection as its connection...

I hope I am enough clear

Merci

Florent Blondeau

Marc Guillemot a écrit :
> Salut Florent,
>
> personally I  set ANT_OPTS to allow remote debugging from Eclipse, ie
> something like
> ANT_OPTS=-Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=4142,suspend
>
> current response is set each time a step loads a new... current response
> and previous response is the value of current response before it get
> changed.
> Normally current response is null only until a response is loaded (a
> previous response gets set when the next current response is loaded).
>
> What are the steps before your filterContent?
>
> Cheers,
> Marc.
>   


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