You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2013/02/21 15:30:13 UTC

[jira] [Created] (DERBY-6086) Factor out logic for creating custom connection in jdbcapi.StatementPoolingTest

Kristian Waagan created DERBY-6086:
--------------------------------------

             Summary: 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


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