Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <0DAD13DC-61BC-40CE-8058-FE640ACD12AA@planet57.com>
References: <c278ac970608040900i21bcc01cr151237539b9aa651@mail.gmail.com>
 <ED992231-D101-4665-B21D-08837465197D@apache.org>
 <0DAD13DC-61BC-40CE-8058-FE640ACD12AA@planet57.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <74DB1627-84F4-48AF-AE5E-FAC395A3F03D@apache.org>
Content-Transfer-Encoding: 7bit
From: Bill Dudney <bdudney@apache.org>
Subject: Re: [itests] Modify the geronimo-deployment-plugin ?
Date: Tue, 8 Aug 2006 17:48:54 -0600
To: dev@geronimo.apache.org

Cool thing is someone else has already done it Cargo currently  
supports G 1.1.

:-)

-bd-

On Aug 8, 2006, at 5:33 PM, Jason Dillon wrote:

> I think that in general it would be good to have cargo support :-)
>
> --jason
>
>
> On Aug 8, 2006, at 4:23 PM, Bill Dudney wrote:
>
>> Hi Prasad,
>>
>> The cargo plugins [1] might be another place to check to start and  
>> stop the server.
>>
>> I've used them before for tomcat and its good stuff for running  
>> integration tests.
>>
>> And what can I do to help?
>>
>> TTFN,
>>
>> -bd-
>>
>> [1] http://cargo.codehaus.org
>>
>> On Aug 4, 2006, at 10:00 AM, Prasad Kashyap wrote:
>>
>>> With the m2migration ready to be merged into trunk, I have resumed
>>> work on the itests for Geronimo again.
>>>
>>> Approx 30% of our code is covered by component level tests that are
>>> embedded in each module. These tests are written as junit test cases
>>> and run by Maven surefire plugin.
>>>
>>> The itests will cover system level tests by testing the
>>> functionalities that an end-user would use on a fully assembled
>>> Geronimo distribution. Therefore to the extent possible, our itests
>>> and it's testcases should use the very same external APIs and
>>> workflows that a user would use.
>>>
>>> We have been using the startRemoteServer and stopRemoteServer  
>>> goals in
>>> the geronimo-deployment-plugin (g-d-p)  to start and stop a  
>>> server. We
>>> have always used these "remote" goals and have never used the in-vm
>>> goals startServer and stopServer.
>>>
>>> I propose that we convert the in-vm goals startServer and stopServer
>>> to be ant mojos from their existing java mojos. Invoking the ant  
>>> mojo
>>> goals in our itests will ensure that our tests are using the same  
>>> APIs
>>> that a end-user uses. Thus we shall no longer use internal hooks in
>>> the code to start and stop the server.
>>>
>>> Thoughts ? Comments ? Advice ?
>>>
>>> Cheers
>>> Prasad
>>
>