Automated testing for frontend
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
For Vue components, see https://vuejs.org/v2/guide/testing.html
For the plain JS code, we could use Jasmine like in the server.
Reason is that we have some quite complex logic both in the JS code (especially webrtc code) and also some Vues like the CallView has a complex set of flags and view switching based on how many screens, videos, etc are available and what mode the user has selected.
For the CallView, ideally we should simplify/refactor it first as I believe it should be possible to achieve the same with simpler code.
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 Vue testing guide linked in the issue and the existing Jasmine-style tests in the server. Identify the Vue components involved, especially CallView, and the plain JavaScript WebRTC logic that needs coverage. Done means the complex view-state and WebRTC behavior has meaningful automated tests, with any CallView simplification treated as a separate prerequisite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- audio-video-rtc, frontend, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100