nextcloud / nextcloud/cookbook
Writing of unit tests
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 641
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
Currently there is a very basic framework to do unit testing in place. However, most parts of the code base are untested. This makes any PR with more than a few lines of changes code very hard to check.
Describe the solution you'd like
Extend the current structure of tests to the whole code base and run these tests (including code coverage checks) on each commit.
Describe alternatives you've considered
The only alternative is to decide not to do any tests and rely on manual testing and hoping for the best.
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 reviewing the existing unit-test structure and how tests are currently run in the repository. Define coverage checks for the code base and commit-level test execution; the work is done when the broader code base is covered and these checks run on each commit.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100