MessageTest-3G Assertions

The MessageTest-3G test case bounds some operations to GET
and DELETE.
For those operations, the test framework checks that the
content-type 
header is set to
"application/x-www-form-urlencoded".
I am wondering whether we should remove these assertions.
What do you think?
Regards,
    Youenn Fablet

I think I agree, and have updated the assertion generator to
omit assertions
about content-type on GET and PUT methods (this isn't a
complete fix - it
doesn't take safety into account, but seems sufficient for
the existing
tests.)

Jonathan Marsh - http://www.wso2.com - http://auburnmar
shes.spaces.live.com
 

> -----Original Message-----
> From: Youenn Fablet [mailto:youenn.fabletcrf.canon.fr]
> Sent: Wednesday, February 21, 2007 6:04 AM
> To: Jonathan Marsh
> Cc: www-ws-desc
> Subject: MessageTest-3G Assertions
> 
> The MessageTest-3G test case bounds some operations to
GET and DELETE.
> For those operations, the test framework checks that
the content-type
> header is set to
"application/x-www-form-urlencoded".
> I am wondering whether we should remove these
assertions.
> What do you think?
> Regards,
>     Youenn Fablet

I agree on GET.
Having a content-type on PUT seems reasonnable to me.
I was also thinking that DELETE may not need a
content-type.
What do you think?
    Youenn

Jonathan Marsh wrote:
> I think I agree, and have updated the assertion
generator to omit assertions
> about content-type on GET and PUT methods (this isn't a
complete fix - it
> doesn't take safety into account, but seems sufficient
for the existing
> tests.)
>
> Jonathan Marsh - http://www.wso2.com - http://auburnmar
shes.spaces.live.com
>  
>
>   
>> -----Original Message-----
>> From: Youenn Fablet [mailto:youenn.fabletcrf.canon.fr]
>> Sent: Wednesday, February 21, 2007 6:04 AM
>> To: Jonathan Marsh
>> Cc: www-ws-desc
>> Subject: MessageTest-3G Assertions
>>
>> The MessageTest-3G test case bounds some operations
to GET and DELETE.
>> For those operations, the test framework checks
that the content-type
>> header is set to
"application/x-www-form-urlencoded".
>> I am wondering whether we should remove these
assertions.
>> What do you think?
>> Regards,
>>     Youenn Fablet
>>     
>
>
>   

Changed PUT to DELETE.

Jonathan Marsh - http://www.wso2.com - http://auburnmar
shes.spaces.live.com
 

> -----Original Message-----
> From: Youenn Fablet [mailto:youenn.fabletcrf.canon.fr]
> Sent: Thursday, February 22, 2007 6:26 AM
> To: Jonathan Marsh
> Cc: 'www-ws-desc'
> Subject: Re: MessageTest-3G Assertions
> 
> I agree on GET.
> Having a content-type on PUT seems reasonnable to me.
> I was also thinking that DELETE may not need a
content-type.
> What do you think?
>     Youenn
> 
> Jonathan Marsh wrote:
> > I think I agree, and have updated the assertion
generator to omit
> assertions
> > about content-type on GET and PUT methods (this
isn't a complete fix -
> it
> > doesn't take safety into account, but seems
sufficient for the existing
> > tests.)
> >
> > Jonathan Marsh - http://www.wso2.com -
> http://auburnmar
shes.spaces.live.com
> >
> >
> >
> >> -----Original Message-----
> >> From: Youenn Fablet [mailto:youenn.fabletcrf.canon.fr]
> >> Sent: Wednesday, February 21, 2007 6:04 AM
> >> To: Jonathan Marsh
> >> Cc: www-ws-desc
> >> Subject: MessageTest-3G Assertions
> >>
> >> The MessageTest-3G test case bounds some
operations to GET and DELETE.
> >> For those operations, the test framework
checks that the content-type
> >> header is set to
"application/x-www-form-urlencoded".
> >> I am wondering whether we should remove these
assertions.
> >> What do you think?
> >> Regards,
> >>     Youenn Fablet
> >>
> >
> >
> >