Test with connection issues for external storages after mounting
Open
Nobody has claimed this yet.
Server
- Dominant language
- Shell
- Stars
- 16
- Forks
- 16
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 1
Description
Steps
- Mount a working external storage, like for example SMB as "/smb"
- Navigate into it, sync it
- Simulate a temporary connection issue with the storage, for example by shutting down the SMB server
- Do a PROPFIND on "/smb" or through web UI
- Restore the connection
- Wait for 10-15 minutes (or clear the "last_checked" column in "oc_storages")
- Check that PROPFIND or web UI has the mount working again
Please note that you should run the test twice, once by doing only PROPFINDs and the other one by only going through the web UI. This is because there different code paths for recovering unavailable storages.
Expected
- ownCloud still works
- syncing still works for other files
- PROPFIND on "/smb" must return 503 StorageNotAvailable when unavailable
- PROPFIND/web UI on "/smb" must work again after the storage has recovered
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use the SMB mount and recovery sequence in the issue as the starting test scenario, covering both PROPFIND and web UI paths. First locate the repository's existing external-storage QA tests and determine how unavailable-storage responses are asserted. Done means both recovery paths are covered and the listed 503, continued operation, and post-recovery expectations pass.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100