db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-2000) A SecurityManager is not always installed when running JUnit tests/suites
Date Wed, 23 May 2007 19:51:16 GMT

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

Daniel John Debrunner resolved DERBY-2000.

       Resolution: Fixed
    Fix Version/s:

COmmitted revision 541044.

Created a new BaseTestSetup class that installs the SecurityManager like BaseTestCase, modified
several decorators to extend this new class rather than TestSetup.

> A SecurityManager is not always installed when running JUnit tests/suites
> -------------------------------------------------------------------------
>                 Key: DERBY-2000
>                 URL: https://issues.apache.org/jira/browse/DERBY-2000
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:
>            Reporter: Kristian Waagan
>         Assigned To: Daniel John Debrunner
>            Priority: Minor
>             Fix For:
>         Attachments: derby-2000-1a.diff
> A SecurityManager is not always installed (early enough) when running JUnit tests/suites.
> For instance, when running 'jdbcapi.BlobClob4Blob' a SecurityManager was installed during
database boot and revealed problems with the policy file, but when the same test was run as
part of 'suites.All', no errors were seen.
> BTW: There is nothing wrong with BlobClob4Blob.
> It seems that 'BaseTestCase.runBare', which installs a SecurityManager, is bypassed when
running code in decorators (most importantly setUp).
> Since a SecurityManager is installed as soon as a test method is run, this bug is not
that severe.

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

View raw message