Re: Test strategy -- itests and default database

2006-02-21 Thread David Blevins
On Jan 29, 2006, at 6:12 AM, Prasad Kashyap wrote: I would like to propose the following test strategy. 1. Fix existing openejb itests such that they can be reintegrated back into the builds. On Feb 9, 2006, at 9:10 AM, Prasad Kashyap wrote: I have completed items 1 and 3 of the test

Re: Test strategy -- itests and default database

2006-02-21 Thread Prasad Kashyap
the following test strategy. 1. Fix existing openejb itests such that they can be reintegrated back into the builds. On Feb 9, 2006, at 9:10 AM, Prasad Kashyap wrote: I have completed items 1 and 3 of the test strategy outlined above. With that we now have the geronimo-deployment-plugin

Re: Test strategy -- itests and default database

2006-02-21 Thread David Blevins
break the infrastructure again without knowing it. Especially with all the maven2 conversion stuff going on. Thanks, -David On 2/21/06, David Blevins [EMAIL PROTECTED] wrote: On Jan 29, 2006, at 6:12 AM, Prasad Kashyap wrote: I would like to propose the following test strategy. 1. Fix

Re: Test strategy -- itests and default database

2006-02-21 Thread Prasad Kashyap
, -David On 2/21/06, David Blevins [EMAIL PROTECTED] wrote: On Jan 29, 2006, at 6:12 AM, Prasad Kashyap wrote: I would like to propose the following test strategy. 1. Fix existing openejb itests such that they can be reintegrated back into the builds. On Feb 9, 2006, at 9:10 AM

Re: Test strategy -- itests and default database

2006-02-21 Thread Dain Sundstrom
On Feb 21, 2006, at 5:28 PM, David Blevins wrote: On Feb 21, 2006, at 2:00 PM, Prasad Kashyap wrote: True. The itests setup (infrastructure) which was broken by the move has been restored. Itests can now be plugged in and run successfully. While some of the old itests pass successfully,

Re: Test strategy -- itests and default database

2006-02-21 Thread David Blevins
On Feb 21, 2006, at 9:15 PM, Dain Sundstrom wrote: On Feb 21, 2006, at 5:28 PM, David Blevins wrote: On Feb 21, 2006, at 2:00 PM, Prasad Kashyap wrote: True. The itests setup (infrastructure) which was broken by the move has been restored. Itests can now be plugged in and run

Re: Test strategy

2006-02-10 Thread Prasad Kashyap
://www.mail-archive.com/dev@geronimo.apache.org/msg16726.html Cheers Prasad On 2/9/06, David Blevins [EMAIL PROTECTED] wrote: On Feb 9, 2006, at 9:10 AM, Prasad Kashyap wrote: I have completed items 1 and 3 of the test strategy outlined above. With that we now have the geronimo-deployment

Re: Test strategy

2006-02-09 Thread Prasad Kashyap
I have completed items 1 and 3 of the test strategy outlined above. With that we now have the geronimo-deployment-plugin in maven 2. I have now begun working on item 2 which is to create a separate itests sub-project that will act as a catchment of the itests from the various modules. Now

Re: Test strategy

2006-02-09 Thread David Blevins
On Feb 9, 2006, at 9:10 AM, Prasad Kashyap wrote: I have completed items 1 and 3 of the test strategy outlined above. With that we now have the geronimo-deployment-plugin in maven 2. What are items 1 and 3? Don't see an outline. -David I have now begun working on item 2 which

Re: Test strategy

2006-01-30 Thread Prasad Kashyap
was quite at the top. http://www.mail-archive.com/dev@geronimo.apache.org/msg16593.html I would like to propose the following test strategy. 1. Fix existing openejb itests such that they can be reintegrated back into the builds. 2. Create a testing subproject first in the sandbox

Re: Test strategy

2006-01-30 Thread Prasad Kashyap
of Dain's Roamap, tasks and things to do list, integration tests that cover servlets, webservices and jms was quite at the top. http://www.mail-archive.com/dev@geronimo.apache.org/msg16593.html I would like to propose the following test strategy. 1. Fix existing openejb itests

Re: Test strategy

2006-01-30 Thread David Blevins
It's probably going to be you doing this work, so ultimately, you are the one who decides what you want to write. I will just say that you and I share the same goals, but your proposal goes against the grain of maven which fundamentally combines build/test. Anytime you do that, it's

Re: Test strategy

2006-01-30 Thread Prasad Kashyap
David, Thanks for letting me make that decision. I, at this point, would now have to get the insight and information from people who are more knowledgeable about the project; something similiar to what you have provided now. With my limited knowledge, I don't want to go down the wrong path. I

Re: Test strategy

2006-01-30 Thread David Blevins
On Jan 30, 2006, at 7:43 PM, Prasad Kashyap wrote: I would like to solicit the views of others too like you and get their views and opinions. Great. I poked some other people in irc to get involved as well. Here is hoping :) More input is going to make for a better community

Test strategy

2006-01-29 Thread Prasad Kashyap
On the list of Dain's Roamap, tasks and things to do list, integration tests that cover servlets, webservices and jms was quite at the top. http://www.mail-archive.com/dev@geronimo.apache.org/msg16593.html I would like to propose the following test strategy. 1. Fix existing openejb itests

Re: Test strategy

2006-01-29 Thread David Blevins
test strategy. 1. Fix existing openejb itests such that they can be reintegrated back into the builds. 2. Create a testing subproject first in the sandbox that can be used to test other services and components. This subproject will use maven 2. Integration test is already a phase in the Maven2