RocketChat / RocketChat/Rocket.Chat
Missing E2E Test for "Username Already Exists" Validation in UI
Open
Nobody has claimed this yet.
area: ui/ux
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description
There is no end-to-end (E2E) test case to verify the UI behavior when a user attempts to register or change their username to an existing one. This validation is crucial to ensure proper error handling and user feedback.
Actual Behaviour
- Currently, there is no automated E2E test to verify this validation.
suggested fix
- Add an E2E test in the appropriate test suite
- Verify that the error message appears when attempting to use an existing username.
- Ensure that submission is blocked until a valid username is entered.
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 locating the E2E suite covering registration or username changes and read the existing username validation tests. Add coverage for submitting an existing username, verify the error message appears, and confirm submission remains blocked until the username is valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100