Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 22 Feb 2013 09:24:14 +0000 (UTC)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12633401.1361456927698.322412.1361525054635@arcas>
In-Reply-To: <JIRA.12633401.1361456927698@arcas>
References: <JIRA.12633401.1361456927698@arcas>
Subject: [jira] [Updated] (DERBY-6086) Factor out logic for creating custom
 connection in jdbcapi.StatementPoolingTest
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kristian Waagan updated DERBY-6086:
-----------------------------------

    Attachment: derby-6086-1b-logical_con_boilerplate.diff
    
> Factor out logic for creating custom connection in jdbcapi.StatementPoolingTest
> -------------------------------------------------------------------------------
>
>                 Key: DERBY-6086
>                 URL: https://issues.apache.org/jira/browse/DERBY-6086
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.10.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-6086-1a-logical_con_boilerplate.diff, derby-6086-1b-logical_con_boilerplate.diff
>
>
> There is quite a bit of common boilerplate code in jdbcapi.StatementPoolingTest related to getting a custom connection, or rather more than one logical connection from a single pooled (physical) connection.
> This could be factored out to make the test methods shorter, and to make the test methods more focused on whatever they're testing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira