[
https://issues.apache.org/jira/browse/DERBY-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470225
]
Kristian Waagan commented on DERBY-2087:
----------------------------------------
For instance when you are testing creation of encrypted databases, with a
strong focus on the inputs specified by the user as connection attributes?
I need to do this somehow in the EncryptionKey test that I said I would convert
to JUnit a long time ago. It might be that it doesn't fit too well with the
current state of the JUnit harness, but it is definitely useful to me for
rewriting that test.
If the usage of such a method goes against "best practice", we should try to
communicate that. You can always do the work yourself in the test, but maybe
it's good have a "single point of entry"?
I'm on thin ice here, as I haven't studied the code, but I think the method
with username and password should be available to the tester. I don't see it as
a requirement that it is available in an internal class.
> Clean up of a database server directory after running junit tests.
> ------------------------------------------------------------------
>
> Key: DERBY-2087
> URL: https://issues.apache.org/jira/browse/DERBY-2087
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Julius Stroffek
> Assigned To: Julius Stroffek
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: d2087.diff, d2087.stat, d2087_round2.diff,
> d2087_round2.stat, d2087_round2_try2.diff, d2087_round2_try2.stat,
> d2087_try2.diff, d2087_try2.stat
>
>
> If I create a test using multiple connections using code like this
> DataSource ds1 = JDBCDataSource.getDataSource("FIRSTDB1");
> JDBCDataSource.setBeanProperty(ds1, "connectionAttributes",
> "create=true");
> Connection conn1 = ds1.getConnection();
> the files created on a server does not get cleaned.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
