[ http://issues.apache.org/jira/browse/DERBY-1141?page=comments#action_12383370 ]
Myrna van Lunteren commented on DERBY-1141: ------------------------------------------- Re the 2nd comment from John, after poking the code, it seems to me the *skip* files were only implemented for skipping of suites, not individual tests. It's not limited to useprocess=false, so I decided this would not be the place to attempt to address it. To implement it, I think something can be added in RunTest.main, in the 'else' block of the call to testRun(propString, sp). > test harness usage of useprocess needs improvement > -------------------------------------------------- > > Key: DERBY-1141 > URL: http://issues.apache.org/jira/browse/DERBY-1141 > Project: Derby > Type: Improvement > Components: Test > Reporter: Myrna van Lunteren > Assignee: Myrna van Lunteren > Attachments: DERBY-1141_20060413.diff, DERBY-1141_20060413.stat, > DERBY-1141_20060424.diff, DERBY-1141_20060424.stat, DERBY-1141_20060512.diff, > JUnit_useprocessFalse_v1.diff > > The 'old' functionTests harness has property useprocess, which, when set to > false, causes tests within a suite to run from within one jvm, thus creating > databases and files in the same directory. > This functionality is useful for debugging test runs within an IDE. > Also, it is potentially useful for speeding up testruns. > However, currently, there are some problems and shortcomings of this > functionality. > - For instance, when running a networkserver test with framework DerbyNet of > type .java one sees the message 'Security Manager not installed' show up > within the test output, thus causing the test to fail. > - running derbynet(client)mats suite with useprocess=false doesn't actually > make things any faster, because networkserver gets started fresh for every > test. > However, it should be feasible to start networkserver with the first test > in a suite, then use that > networkserver for subsequent tests and shutdown networkserver when the > suite finishes. > - Also, (reported by Mike Matrigali off-list) currently, the following: > ------------------ > java -Duseprocess=false -Doutputdir=<snippeddirname>/newout -Dkeepfiles=true > org.apache.derbyTesting.functionTests.harness.RunTest lang/closed.java > ------------------ > makes the test fall out of the harness with: Exception in thread "main" > and in the .tmp: > ------------------ > java.security.AccessControlException: access denied (java.io.FilePermission > <snippeddirname>\newout read) > at > java.security.AccessControlContext.checkPermission(AccessControlContext.java:269) > at > java.security.AccessController.checkPermission(AccessController.java:401) > at java.lang.SecurityManager.checkPermission(SecurityManager.java:524) > at java.lang.SecurityManager.checkRead(SecurityManager.java:863) > at java.io.File.exists(File.java:678) > at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:360) > at java.io.File.getCanonicalPath(File.java:513) > at > org.apache.derbyTesting.functionTests.harness.RunTest.execTestNoProcess(RunTest.java:2370) > at > org.apache.derbyTesting.functionTests.harness.RunTest.testRun(RunTest.java:443) > at > org.apache.derbyTesting.functionTests.harness.RunTest.main(RunTest.java:302) > -------------------------------- > removing the -Doutputdir gets around that problem, but shouldn't be needed. > - there is the reference > http://www.nabble.com/AccessControlException-when-running-functional-tests-t1321374.html#a3526947 > I couldn't duplicate this yet, maybe more info to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
