Idea #4387
Updated by Tom Clegg over 9 years ago
Additional tests of the FUSE driver that would be useful. Discussed in #4040. * Authenticate as the @fuse@ user (rather than as @admin@) to ensure so we can evaluate in test how the filesystem is correctly presented to an the unprivileged user. E.g., Would allow us to test that e.g. projects shared with @fuse@ appear in the expected place. * Contents of collections and multilevel collections ** Will probably require seeding KEEP_LOCAL_STORE with blocks that match a known manifest * Subprojects within projects * Read file contents (already satisfied by FuseMountTest?) * Multilevel collections (already satisfied by "edgecases" in FuseMountTest, from #4363?) Note: Avoid testing Projects shared with a user via permission link (probably requires authenticating as the permission system itself @fuse@ user -- 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). see above)