[Installation tests] Distribution upgrades definition
Open
Nobody has claimed this yet.
Desktop client
help wanted
- Dominant language
- Shell
- Stars
- 16
- Forks
- 16
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 1
Description
In last call with @moscicki we reached an interesting conclusion for the automated installation tests (ref. https://github.com/owncloud/platform/issues/81). I had only considered one kind of upgrade tests, i.e. client itself being upgraded (e.g. from v.2.2.4 to v.2.3) but he pointed out to an also interesting use-case for many users: the distribution upgrade.
Some notes:
- We need some input on which upgrade paths would be of interest. (e.g. some data on which distributions are the most upgraded) - ... or if this should be done with all supported distros. Note that one reason to consider this is the time-consuming nature of this operation.
- Also, any relevant data on how the users perform upgrades (using the package managers:
apt-get dist-upgradeon Deb/Ubu, scripts, manually...)
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
The issue names no files, tests, or entry points. Start by gathering data on commonly upgraded distributions and user upgrade methods, then define the distribution upgrade paths and package-manager or manual procedures that the automated installation tests should cover.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100