RocketChat / RocketChat/EmbeddedChat
Improve Playwright Test Coverage and Stability to Eliminate Manual UI Testing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 165
- Forks
- 381
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
As an EmbeddedChat developer
I need to:
Strengthen and expand Playwright test coverage for PR-related flows and UI interactions.
So That:
We can rely on automated tests instead of manually testing changes locally or through the UI, improving reliability and development speed.
Acceptance Criteria
- Tests are stable, deterministic, and do not fail due to timing or flaky selectors
- Mocking or test fixtures are used where appropriate to avoid dependency on external services
- Tests run successfully in CI without requiring manual setup
- Clear failure messages are provided to help debug issues quickly
- Test execution time is optimized and does not significantly slow down CI pipelines
Contributor guide
No contributing guide indexed for this repository
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, test suites, or entry points; start by locating the existing Playwright tests for PR-related flows and UI interactions. Compare their CI behavior and failure output against the acceptance criteria, then confirm stability, fixture or mocking coverage, CI execution, diagnostics, and runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100