Automated tests for files_versions
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 16
- Forks
- 16
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 1
Description
The app doesn't have public endpoints but we could use the private ones in the time being.
Tests like:
- overwriting a file multiple times creates versions
- version can be downloaded and contains the old content
- file can be restored to old version, download it contains the old content
- preview correctly returned (no error) for the version file (same URL as rendered in versions panel)
- restoring a version still works if no delete permission on target file
- all of the above with trashbin: delete a file that has versions, restore the file and check that the versions still work (download/restore)
- all of the above with encryption (including the trashbin one)
- all of the above with received shared files
@owncloud/qa
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
Start by locating the private endpoints for files_versions and the existing automated-test entry points. Cover version creation, download, preview, restoration, trashbin behavior, encryption, and received shared files; done means the listed scenarios pass without errors.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100