[User Stories 1] As a end-user have a screen for registration page to create the login details to access the applicattions

[RameshAravindhAT]

User Story: Registration Page for Creating Login Details **

As a: End-user
I want: A screen for registration to create my login details
So that: I can access the application securely.

---

Acceptance Criteria **:

1. Registration Page UI **:

   • The page must have a clean and user-friendly interface.
   • The following fields must be present on the registration page:
     • Full Name: Input field for the user to enter their full name.
     • Email Address: Input field for the user to enter a valid email address.
     • Password: Input field for the user to create a password (should be masked for privacy).
     • Confirm Password: Input field to confirm the password.
     • Phone Number: Optional input field for the user’s phone number.
     • Date of Birth: Optional field for the user’s date of birth (if applicable).
     • Terms and Conditions Checkbox: The user must agree to the terms and conditions before proceeding with registration.
     • Submit Button: A button to submit the registration details.

2. Field Validations **:

   • Full Name: Must be at least 2 characters long and should not contain special characters or numbers.
   • Email Address:
     • Must be a valid email format (e.g., user@example.com).
     • Must not already be registered (system should check for duplicate email addresses).
   • Password:
     • Must be at least 8 characters long.
     • Must contain at least one uppercase letter, one lowercase letter, one digit, and one special character (e.g., @, #, $).
     • Should not be the same as the email address.
   • Confirm Password:
     • Must match the password entered in the "Password" field.
     • If passwords do not match, show an error message.
   • Phone Number: If entered, must follow a valid phone number format (e.g., with country code).
   • Date of Birth: If entered, must be a valid date format and ensure the user is at least 18 years old (if applicable).
   • Terms and Conditions: The checkbox must be checked before the user can proceed with registration.

3. Error Messages **:

   • If any field fails validation (e.g., incorrect email format, password mismatch), appropriate error messages should be displayed near the respective field.
   • Error messages should be clear, concise, and specific, such as "Please enter a valid email address," "Passwords do not match," "Password must contain at least 8 characters," etc.

4. Registration Process **:

   • Upon successful validation, the user should be able to click the Submit Button to proceed with account creation.
   • The registration form should submit and save the user's details to the backend.
   • The user should receive a confirmation message or email indicating successful registration.

5. Redirection **:

   • After successful registration, the user should be redirected to a Login Page where they can enter their newly created login details (email and password).
   • If there is an error during registration (e.g., duplicate email), an error message should be shown to the user without submitting the form.

6. Security **:

   • Passwords should be stored securely using encryption (hashed and salted).
   • User data should be protected in accordance with data privacy regulations (e.g., GDPR).
   • The registration form should implement CAPTCHA or another anti-bot mechanism to prevent automated submissions (optional but recommended).

7. Responsiveness **:

   • The registration page should be fully responsive and accessible on mobile devices, tablets, and desktops.
   • All fields and buttons should resize appropriately on different screen sizes.

8. Accessibility **:

   • All form fields should have proper labels and be accessible to screen readers.
   • The page should follow WCAG accessibility guidelines to ensure users with disabilities can use the registration page effectively.

9. Confirmation Email (Optional, but best practice):

   • After the registration is successfully completed, a confirmation email should be sent to the provided email address with an activation link or verification code (if email verification is part of the process).

10. Additional Notes **:

    • If the user tries to submit an incomplete form or skips any mandatory fields, a message should be shown indicating that all required fields need to be filled out.

---

Example Success Scenario **:

• A user visits the registration page, enters their full name, email, password, confirms the password, and agrees to the terms and conditions.
• They click Submit, the form passes validation, and they are redirected to the login page with a success message.

---

Example Failure Scenario **:

• A user enters an invalid email address (e.g., "john.doe.com") and tries to submit the form.
• The system shows an error message next to the email field saying, "Please enter a valid email address."

---

This refactor includes the required formatting with ** added to headers and subheaders. Let me know if you need any further adjustments!

[ragul0106]

Hi @RameshAravindhAT ,

I have done this registration feature so please carry on the positive and negative testing

[RameshAravindhAT]

HI @ragul0106 ,

This feature has bug. Please do the correction and send it back.

[RameshAravindhAT]

Hi @ragul0106 ,

Please rework on the issue for the entire screen for the development

[RameshAravindhAT]

Hi @anithaviswa ,

Please under the req and work as same

[anithaviswa]

hii @RameshAravindhAT

screen as developed .Please continue on the testing .

[RameshAravindhAT]

Hi @anithaviswa ,

So I have done the testing, The build is not stable please rework on the isue

[anithaviswa]

hii @RameshAravindhAT

i have reworked on the bug fixes .Plese do the retesting.

[RameshAravindhAT]

Hi @ragul0106 @anithaviswa @RameshAravindhAT

Complete this user stories