You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Samisa Abeysinghe <sa...@wso2.com> on 2008/06/27 07:49:46 UTC
Test suite for transports [was: Re: Test suite for HTTP transport]
Supun Kamburugamuva wrote:
> Do you think this is the correct discussion for refactoring the
> transport? Or I'm I missing something?
OK, I fixed the subject :)
I think, in addition to what you have mentioned, the testing should also
verify:
1. Content received and content sent
2. Transport specific stuff such as content length, chunk verification etc.
3. Handling of REST cases vs. SOAP cases (right now we have these
associated with transports, logically speaking, that is not right,
because REST and SOAP should be at a higher level. Still since the
current code have them, we have to have tests for those. After
refactoring, we should ideally have those REST and SOAP chunks of logic
on top of transports. In fact, REST is tightly bound to HTTP, but that
does not mean that we cannot do POX like transactions using other
transports as well)
4. There should also be tests that cover the interface between transport
and other layers that use the transport
Thanks,
Samisa...
>
> Supun..
>
> On Fri, Jun 27, 2008 at 10:09 AM, Supun Kamburugamuva
> <supun06@gmail.com <ma...@gmail.com>> wrote:
>
> Hi list,
>
> These are the key areas that comes to my mind that we should focus
> on for testing.
>
> 1. It should work for all sorts of HTTP scenarios. Headers and
> data are the key things. We can focus on different combinations.
> 2. Should not leak memory
> 3. Should have good performance characteristics
>
> Thoughts?
>
> Supun..
>
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG.
> Version: 8.0.101 / Virus Database: 270.4.1/1521 - Release Date: 6/26/2008 11:20 AM
>
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: Test suite for transports [was: Re: Test suite for HTTP transport]
Posted by Samisa Abeysinghe <sa...@wso2.com>.
Manjula Peiris wrote:
> So is this mean we first design and implement the test cases and then
> test current code using these test cases. After that we refactor the
> transport ?
>
Yes. I hope that is the correct approach IMHO.
Samisa...
> On Fri, 2008-06-27 at 11:19 +0530, Samisa Abeysinghe wrote:
>
>> Supun Kamburugamuva wrote:
>>
>>> Do you think this is the correct discussion for refactoring the
>>> transport? Or I'm I missing something?
>>>
>> OK, I fixed the subject :)
>>
>> I think, in addition to what you have mentioned, the testing should also
>> verify:
>>
>> 1. Content received and content sent
>> 2. Transport specific stuff such as content length, chunk verification etc.
>> 3. Handling of REST cases vs. SOAP cases (right now we have these
>> associated with transports, logically speaking, that is not right,
>> because REST and SOAP should be at a higher level. Still since the
>> current code have them, we have to have tests for those. After
>> refactoring, we should ideally have those REST and SOAP chunks of logic
>> on top of transports. In fact, REST is tightly bound to HTTP, but that
>> does not mean that we cannot do POX like transactions using other
>> transports as well)
>> 4. There should also be tests that cover the interface between transport
>> and other layers that use the transport
>>
>> Thanks,
>> Samisa...
>>
>>
>>> Supun..
>>>
>>> On Fri, Jun 27, 2008 at 10:09 AM, Supun Kamburugamuva
>>> <supun06@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Hi list,
>>>
>>> These are the key areas that comes to my mind that we should focus
>>> on for testing.
>>>
>>> 1. It should work for all sorts of HTTP scenarios. Headers and
>>> data are the key things. We can focus on different combinations.
>>> 2. Should not leak memory
>>> 3. Should have good performance characteristics
>>>
>>> Thoughts?
>>>
>>> Supun..
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG.
>>> Version: 8.0.101 / Virus Database: 270.4.1/1521 - Release Date: 6/26/2008 11:20 AM
>>>
>>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG.
> Version: 8.0.101 / Virus Database: 270.4.1/1521 - Release Date: 6/26/2008 11:20 AM
>
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: Test suite for transports [was: Re: Test suite for HTTP
transport]
Posted by Manjula Peiris <ma...@wso2.com>.
So is this mean we first design and implement the test cases and then
test current code using these test cases. After that we refactor the
transport ?
On Fri, 2008-06-27 at 11:19 +0530, Samisa Abeysinghe wrote:
> Supun Kamburugamuva wrote:
> > Do you think this is the correct discussion for refactoring the
> > transport? Or I'm I missing something?
>
> OK, I fixed the subject :)
>
> I think, in addition to what you have mentioned, the testing should also
> verify:
>
> 1. Content received and content sent
> 2. Transport specific stuff such as content length, chunk verification etc.
> 3. Handling of REST cases vs. SOAP cases (right now we have these
> associated with transports, logically speaking, that is not right,
> because REST and SOAP should be at a higher level. Still since the
> current code have them, we have to have tests for those. After
> refactoring, we should ideally have those REST and SOAP chunks of logic
> on top of transports. In fact, REST is tightly bound to HTTP, but that
> does not mean that we cannot do POX like transactions using other
> transports as well)
> 4. There should also be tests that cover the interface between transport
> and other layers that use the transport
>
> Thanks,
> Samisa...
>
> >
> > Supun..
> >
> > On Fri, Jun 27, 2008 at 10:09 AM, Supun Kamburugamuva
> > <supun06@gmail.com <ma...@gmail.com>> wrote:
> >
> > Hi list,
> >
> > These are the key areas that comes to my mind that we should focus
> > on for testing.
> >
> > 1. It should work for all sorts of HTTP scenarios. Headers and
> > data are the key things. We can focus on different combinations.
> > 2. Should not leak memory
> > 3. Should have good performance characteristics
> >
> > Thoughts?
> >
> > Supun..
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> > No virus found in this incoming message.
> > Checked by AVG.
> > Version: 8.0.101 / Virus Database: 270.4.1/1521 - Release Date: 6/26/2008 11:20 AM
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org