Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <417052043.1232642399719.JavaMail.jira@brutus>
Date: Thu, 22 Jan 2009 08:39:59 -0800 (PST)
From: "B.J. Reed (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Closed: (GERONIMODEVTOOLS-541) move all Abbot testcases to
 run during a single server install/uninstall
In-Reply-To: <1215364244.1228341224477.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

B.J. Reed closed GERONIMODEVTOOLS-541.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.0
         Assignee: B.J. Reed  (was: Tim McConnell)

Fixed with r736695 in trunk.  Use Eclipse Extension Points and Extensions for each new test case.  The EclipseUITest is now the driver for the testsuite. It does a quick sanity check to verify the Geronimo installation, starts the server, and then calls each Test Case Extension to build, run, and clean the test.  After all are finished, it uninstalls the server.

> move all Abbot testcases to run during a single server install/uninstall
> ------------------------------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-541
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-541
>             Project: Geronimo-Devtools
>          Issue Type: Sub-task
>          Components: eclipse-plugin
>            Reporter: B.J. Reed
>            Assignee: B.J. Reed
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> For each Abbot test case, each test case creates a new server, starts the server, stops the server, and then removes the server.  This is very time consuming for the test cases to run and ends up testing much of the same code over and over again.
> It would be better to change the test suite to really only have one test (for each server version) with everything else done while the server is running.  So the algorithm should be:
> check valid GEP installation
> create server
> start server
> test A
> test A cleanup
> test B
> test B cleanup
> .....
> stop server
> remove server

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.