This class is utility class, in most situations it is extended by a
another class to write the test.
If you are looking to to provide abstractions for connections you can
certainly/override the "getConnection" calls or add others. You can
refactor to suit the needs, I just wondering if that requires pushing
the functionality to a base class (as this is already functionally a
On Thu, 2009-08-27 at 09:59 -0500, Van Halbert wrote:
I would like to refactor AbstractMMQueryTestCase by pushing its core
logic further down (new base class) for executing queries, comparing
results, and common actions on the connection, etc. so that it can
reused (extended) for any manner of tests that, in the end, use a
Connection. Also, this core logic is basic to jdbc testing and
therefore would like to reuse this in the, soon to becoming,
integration test project for testing transactions and running the ctc
tests. There was already a similar class, from whence it came
from, in the JBEDSP integration test project. So I would to
consolidate this logic.
Any comments, complaints, suggestions, please speak up. Otherwise I
will commence with refactoring tomorrow.
Principal Software Eng.
Red Hat, Inc.
teiid-dev mailing list