Hi Supun, Actually what you have mentioned about HTTP transport is correct. But we have to consider other transports as well. I think you forgot them somehow ;-). I think what we have to test is the functionality of Axis2/C engine when it uses different transports. We have to make sure that Axis2/C engine behave as in the way that Web Services engine must behave even though it's run on different different transports. We must design some test cases that help us to identify abnormal behaviors in basic functionality(if there are any :)) when we use each of the transports we currently support. We can design test cases that check each transport related things separately and web services engine related things separately. Please feel free to comment on this.
thank milinda... On Fri, Jun 27, 2008 at 10:20 AM, Supun Kamburugamuva <[EMAIL PROTECTED]> wrote: > Do you think this is the correct discussion for refactoring the transport? > Or I'm I missing something? > > Supun.. > > > On Fri, Jun 27, 2008 at 10:09 AM, Supun Kamburugamuva <[EMAIL PROTECTED]> > 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.. > > > -- http://mpathirage.com http://wso2.org "Oxygen for Web Service Developers" http://wsaxc.blogspot.com "Web Services With Axis2/C"
