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 "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2007/05/23 21:36:16 UTC
[jira] Assigned: (DERBY-2000) A SecurityManager is not always
installed when running JUnit tests/suites
[ https://issues.apache.org/jira/browse/DERBY-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel John Debrunner reassigned DERBY-2000:
--------------------------------------------
Assignee: Daniel John Debrunner
> 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: 10.3.0.0
> Reporter: Kristian Waagan
> Assigned To: Daniel John Debrunner
> Priority: Minor
> 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.