nextcloud / nextcloud/whiteboard
Testing
Open
Nobody has claimed this yet.
tests
- Dominant language
- JavaScript
- Stars
- 215
- Forks
- 39
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
- Simple e2e frontend tests opening, closing a whiteboard, verifying that changes are saved
- PHP Backend
- Integration tests for API endpoints
- Unit tests where feasible
- Websocket backend
- Unit test where it makes sense
- Think about how to cover the websocket backend with tests -> https://github.com/nextcloud/whiteboard/pull/146
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 checklist in the issue and the linked pull request about covering the websocket backend. Identify the existing frontend, PHP API, and websocket test entry points before choosing a focused area. Done means the relevant end-to-end, integration, unit, or websocket coverage is implemented and passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- backend, frontend, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100