nextcloud / nextcloud/cookbook
Drop unneeded migration tests
Open
Nobody has claimed this yet.
maintenance
meta and development
- Dominant language
- HTML
- Stars
- 641
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
Check (and think!) if the migration tests are actually needed and eventually drop them from the code base.
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
Locate the migration test files and read what behavior they cover before deciding whether they are still needed. Check their relationship to the migration code and existing test coverage; done means either documenting why they must remain or removing the unnecessary tests without reducing required coverage.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100