-
Notifications
You must be signed in to change notification settings - Fork 95
Open
Description
User story:
As a registered user, I want to be able to sign in to my account using my credentials, So that I can access personalized features and data within the application.
Acceptance criteria:
- The sign-in form should include mandatory fields for entering email and password, “Sign In” button, “Sign Up” button.
- The Email field should consist of a local and a domain part separated by a symbol @ and accept lowercase latin letters, uppercase latin letters, digits, special characters, dot.
- When a user enters an invalid email address he should get an error message “Please, enter a correct email”.
The same approach is for password - If a user leaves an email or password field empty, this field should be highlighted in red and the “This field is required” error message should be displayed next to this field, indicating that they are mandatory.
- Validation shared with BE
- When a user clicks the “Sign In” button, the service should perform validation that the password and email mandatory fields are filled in and data should be sent to the back-end for validation and authentication.
- If authentication is successful, the user should be redirected to the application’s main page.(currently root page).
- Store received token into localstorage
- If authentication fails, the “Login failed. Invalid Email or Password” error message should be displayed indicating failure.
Clicking the “Sign Up” button successfully redirects to the sign-up page.