+1 from me Rajith
On 1/1/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
The security tests are among the slowest integration tests that we've got. If there's a way, as Ruchith and Deepal mention, to actually test the same Axis2 functionality without the full security machinery, that would serve two purposes - speeding up the build and also more cleanly reducing the coupling between core Axis2 and other modules. I'd love to see that happen. The Rampart build will of course still test the full Axis2/security integration, we'd just be focusing the Axis2 tests more appropriately. That said, +1 from me too. :) --Glen Eran Chinthaka wrote: > I think I mentioned this couple of times earlier also. > > Security tests provide very good integration tests for Axis2 and if you > have developed Axis2, those are the hard tests to get passed when you > are doing changes. Yes, I agree that we didn't have Axis2 specific tests > to cover most of the integration tests these security tests are > covering. Removing them to reduce the build time is not a very good idea > at all. > > At the same time, if the ecurity related modules are moved out of Axis2, > then all these tests also must be moved out. I am sorry that I am not > in a position to help with it these days, but it would be great if some > one can write tests to cover the scenarios security tests were covering, > before Rampart is moved out. As if we defer that, then it won't happen :) > > HEre is my +1 with the above comments. > > -- Chinthaka > > > Ruchith Fernando wrote: >> Deepal, >> >> Do you think we have tests to cover the axis2 functionality that those >> test covers? >> >> If so or if someone volunteers to write some then lets remove the >> rampart integration tests. >> >> Thanks, >> Ruchith >> >> On 1/1/07, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: >>> I think its better if we can move some of integration test cases , b'coz >>> that will help us to reduce Axis2 build time. >>> >>> Thanks >>> Deepal >>> >>> Ruchith Fernando wrote: >>> >>> > I prefer to leave the tests in axs2 since they do test a lot of axis2 >>> > stuff such as xmlbeans codegen, holding and accessing properties on >>> > context hierarchy, etc. >>> > >>> > I will have those + some more tests in the new rampart project. >>> > >>> > Thanks, >>> > Ruchith >>> > >>> > On 12/30/06, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: >>> > >>> >> +1 from me too.. >>> >> >>> >> BTW what are your plans for the integration tests... >>> >> >>> >> ~Thilina >>> >> >>> >> On 12/30/06, Chuck Williams <[EMAIL PROTECTED]> wrote: >>> >> > +1 >>> >> > >>> >> > Chuck >>> >> > >>> >> > David Illsley wrote on 12/29/2006 05:44 AM: >>> >> > > +1 from me. >>> >> > > >>> >> > > David >>> >> > > >>> >> > > On 29/12/06, Paul Fremantle <[EMAIL PROTECTED]> wrote: >>> >> > >> +1 from me. >>> >> > >> >>> >> > >> Paul >>> >> > >> >>> >> > >> On 12/29/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: >>> >> > >> > +1 from me. It's time :) >>> >> > >> > >>> >> > >> > -- dims >>> >> > >> > >>> >> > >> > On 12/29/06, Ruchith Fernando <[EMAIL PROTECTED]> >>> wrote: >>> >> > >> > > Hi All, >>> >> > >> > > >>> >> > >> > > We released Rampart-1.1 on the 10th December and I think >>> it is >>> >> > >> time to >>> >> > >> > > get all rampart related code out of Axis2 into a new >>> >> sub-project of >>> >> > >> > > the Apache Web services project. >>> >> > >> > > >>> >> > >> > > I propose we call this new project "Rampart" and include >>> >> code from >>> >> > >> > > rampart, rahas and secpolicy maven modules of axis2. These >>> >> will be >>> >> > >> > > called rampart-core, rampart-trust and rampart-policy >>> >> respectively. >>> >> > >> > > >>> >> > >> > > Here's my +1 >>> >> > >> > > >>> >> > >> > > Thanks, >>> >> > >> > > Ruchith >>> >> > >> > > >>> >> > >> > > -- >>> >> > >> > > www.ruchith.org >>> >> > >> > > www.wso2.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
