Closed
Bug 1038901
Opened 10 years ago
Closed 8 years ago
[testing] Test to verify duplicate usernames are not allowed
Categories
(Mozilla QA Graveyard :: One and Done, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bitgeeky, Assigned: tlnob, NeedInfo)
Details
Attachments
(1 file)
This test is to verify that a user cannot create/edit profile with an already existing username.
Reporter | ||
Updated•10 years ago
|
Assignee: nobody → mozpankaj1994
Reporter | ||
Comment 1•10 years ago
|
||
Working on this.
Reporter | ||
Comment 2•10 years ago
|
||
Test Case: 1 Create an existing user using user API 2 Login as a new user and try to register with the same username as that of existing user 3 Assert that the home registration page displays even after clicking save profile button 4 Assert appropriate error gets displayed, error to change username 5 Register the new user with a different username 6 Navigate to user profile page 7 Try to change username and set it to the username of existing user 8 Assert error gets displayed 9 Assert the page is still edit profile page
Reporter | ||
Comment 3•10 years ago
|
||
10 Enter a new username and save profile 11 Assert that the displayed page is home page
Reporter | ||
Comment 4•10 years ago
|
||
Test passes locally and on staging website.
Attachment #8459884 -
Flags: review?(bob.silverberg)
Comment 5•8 years ago
|
||
we have decided not to add the test in this manner.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•8 years ago
|
Attachment #8459884 -
Flags: review?(bob.silverberg)
Comment 6•8 years ago
|
||
Actually, we could still have this test case, but the approach to writing it needs to be different. We would make it a local-only test and use FactoryBoy to pre-populate data. I am going to reopen this as it is still a test that could be worked on, but it would need to start from scratch with a new PR.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 7•8 years ago
|
||
bitgeeky, I am going to unassign it from you as I don't know if you still have time and interest in working on it, but if you want to take it again you are free to do so.
Assignee: mozpankaj1994 → nobody
Comment 9•8 years ago
|
||
Varna- This issue and the other one are still open. Please choose one to start with, and submit your pull request to https://github.com/mozilla/oneanddone. Mention this bug # in the pull request. Thanks!
Comment 10•8 years ago
|
||
I've assigned bug 1043794. I'd prefer to leave this one for another contributor, or at least wait until your changes have landed in bug 1043794. Thanks.
Assignee | ||
Comment 11•8 years ago
|
||
Hello, I would like to be assigned for this bug in order to get a patch in Outreachy. Could you please assign me?
Flags: needinfo?(thais.nobre7)
Assignee | ||
Comment 12•8 years ago
|
||
(In reply to Thais (:tlnob) from comment #11) > Hello, > I would like to be assigned for this bug in order to get a patch in > Outreachy. > Could you please assign me?
Assignee | ||
Updated•8 years ago
|
Flags: needinfo?(thais.nobre7)
Comment 13•8 years ago
|
||
Thanks Thais, I've now assigned the bug to you.
Assignee: nobody → thais.nobre7
Comment 15•8 years ago
|
||
Project is being retired.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•