Actions
Idea #4387
closed
[Tests] additional FUSE tests
Status:
Resolved
Priority:
Normal
Assigned To:
-
Category:
Tests
Target version:
-
Story points:
0.5
Description
Additional tests of the FUSE driver that would be useful. Discussed in #4040.
- Authenticate as the
fuseuser (rather than asadmin) to ensure the filesystem is correctly presented to an unprivileged user. E.g., projects shared withfuseappear in the expected place. - Subprojects within projects
- Read file contents (already satisfied by FuseMountTest?)
- Multilevel collections (already satisfied by "edgecases" in FuseMountTest, from #4363?)
Note: Avoid testing the permission system itself -- that's the job of the API server's test suite. Just test the way various permission scenarios are handled/exposed by FUSE (e.g., a project is visible, but its parent project is not visible).
Updated by Radhika Chippada over 9 years ago
It would also help tremendously if the variables such as d1, d2, d3 etc in the "test_mount.py" are given self explanatory names as was done in "FuseSharedTest" class.
Updated by Tom Clegg over 9 years ago
- Description updated (diff)
- Story points set to 0.5
Updated by Tom Clegg about 8 years ago
- Status changed from New to Resolved
- Target version deleted (
Arvados Future Sprints)
Looks like we've managed to cover all of the cases without updating this issue.
- IntegrationTest subclasses use the non-admin 'active' user
- FuseProjectMvTest does project-in-project
- Lots of tests do read-file-data
- FuseMountTest "edgecases" section does multilevel collection
Actions