[ https://issues.apache.org/jira/browse/VFS-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899202#comment-13899202 ]
Gary Gregory commented on VFS-514: ---------------------------------- The order of @Test method execution is effectively random. Patch applied, thank you. {noformat} commit -m "<action issue="VFS-514" dev="ggregory" type="update" due-to="Bernd Eckenfels">..." C:/vcs/svn/apache/commons/trunks-proper/vfs/src/changes/changes.xml C:/vcs/svn/apache/commons/trunks-proper/vfs/core/src/test/java/org/apache/commons/vfs2/test/PermissionsTests.java Sending C:/vcs/svn/apache/commons/trunks-proper/vfs/core/src/test/java/org/apache/commons/vfs2/test/PermissionsTests.java Sending C:/vcs/svn/apache/commons/trunks-proper/vfs/src/changes/changes.xml Transmitting file data ... Committed revision 1567656. {noformat} > [tests] PermissionsTests leaves unclean test directory > ------------------------------------------------------ > > Key: VFS-514 > URL: https://issues.apache.org/jira/browse/VFS-514 > Project: Commons VFS > Issue Type: Bug > Affects Versions: 2.0 > Environment: CentOS x64 Maven 3.1 build Java 7u51 > Reporter: Bernd Eckenfels > Priority: Minor > Labels: test > Fix For: 2.1 > > Attachments: VFS-514-permission.patch > > > As discussed in VFS-500 the RamProviderTestCase fails with > FileNotFoundException in setUp() if it is running after the PermissionTest of > LocalProviderTestCase. The attached patch will make sure the test file with > the limited permissions will be removed after the test run. It also makes > sure to name the file a bit easier to correlate with the test. It also fixes > some copy+paste errors in comments. It also moves the test functions together > (moves the private helper functions to the end of the file). > I am not sure why not all tests fail and why the problem occurs more often > with VFS-500 applied. Could be a sequence thing? -- This message was sent by Atlassian JIRA (v6.1.5#6160)