TEST TYPE: dashboard_functional Title: TC_FUNC_01_Valid_Login Scenario: User logs in with valid credentials. Steps to reproduce: 1. Enter valid username. 2. Enter valid password. 3. Click on the "Login" button. Expected Result: User is successfully logged into the dashboard. Actual Result: [To be filled during execution] Priority: High Title: TC_FUNC_02_Invalid_Login Scenario: User attempts login with invalid credentials. Steps to reproduce: 1. Enter invalid username. 2. Enter invalid password. 3. Click on the "Login" button. Expected Result: Error message displayed indicating invalid credentials. Actual Result: [To be filled during execution] Priority: High Title: TC_FUNC_03_Empty_Username Scenario: User attempts to login without entering a username. Steps to reproduce: 1. Leave the username field empty. 2. Enter a valid password. 3. Click on the "Login" button. Expected Result: Error message displayed indicating username is required. Actual Result: [To be filled during execution] Priority: Medium Title: TC_FUNC_04_Empty_Password Scenario: User attempts to login without entering a password. Steps to reproduce: 1. Enter a valid username. 2. Leave the password field empty. 3. Click on the "Login" button. Expected Result: Error message displayed indicating password is required. Actual Result: [To be filled during execution] Priority: Medium Title: TC_FUNC_05_Remember_Me_Functionality Scenario: User selects "Remember me" and logs in. Steps to reproduce: 1. Enter valid username. 2. Enter valid password. 3. Select "Remember me" checkbox. 4. Click on the "Login" button. 5. Logout and return to the login page. Expected Result: Username is pre-filled in the username field. Actual Result: [To be filled during execution] Priority: Low Title: TC_FUNC_06_Forgot_Password_Link Scenario: User clicks on "Forgot password?" link. Steps to reproduce: 1. Click on "Forgot password?" link. Expected Result: User is redirected to the password recovery page. Actual Result: [To be filled during execution] Priority: Medium Title: TC_FUNC_07_Register_Link Scenario: User clicks on "Register" link. Steps to reproduce: 1. Click on "Register" link. Expected Result: User is redirected to the registration page. Actual Result: [To be filled during execution] Priority: Medium Title: TC_FUNC_08_Username_Field_Validation Scenario: Username field validation for special characters. Steps to reproduce: 1. Enter special characters in the username field. 2. Enter a valid password. 3. Click on the "Login" button. Expected Result: Error message displayed indicating invalid username format. Actual Result: [To be filled during execution] Priority: Low Title: TC_FUNC_09_Password_Field_Validation Scenario: Password field validation for minimum length. Steps to reproduce: 1. Enter a valid username. 2. Enter a password shorter than required length. 3. Click on the "Login" button. Expected Result: Error message displayed indicating password is too short. Actual Result: [To be filled during execution] Priority: Low Title: TC_FUNC_10_Visible_Password_Toggle Scenario: Password visibility toggle functionality. Steps to reproduce: 1. Enter a valid password. 2. Click on the visibility toggle icon in the password field. Expected Result: Password is toggled between visible and hidden. Actual Result: [To be filled during execution] Priority: Low Title: TC_FUNC_11_Tab_Order_Navigation Scenario: Validate tab order navigation through fields. Steps to reproduce: 1. Press the "Tab" key to navigate through fields. Expected Result: Cursor moves logically from username to password to login button. Actual Result: [To be filled during execution] Priority: Low Title: TC_FUNC_12_Login_Button_Disabled Scenario: Login button disabled when fields are empty. Steps to reproduce: 1. Leave both username and password fields empty. Expected Result: "Login" button is disabled. Actual Result: [To be filled during execution] Priority: Medium Title: TC_FUNC_13_Case_Sensitivity_Username Scenario: Check case sensitivity of the username field. Steps to reproduce: 1. Enter username in different cases (e.g., uppercase). 2. Enter valid password. 3. Click on the "Login" button. Expected Result: Login is successful only if the case matches. Actual Result: [To be filled during execution] Priority: Low Title: TC_FUNC_14_Session_Timeout_After_Login Scenario: Validate session timeout functionality after login. Steps to reproduce: 1. Log in with valid credentials. 2. Remain inactive for a period exceeding session timeout. Expected Result: User is logged out automatically after session timeout. Actual Result: [To be filled during execution] Priority: Medium Title: TC_FUNC_15_Cross_Browser_Compatibility Scenario: Check login functionality across different browsers. Steps to reproduce: 1. Open the login page in different browsers (Chrome, Firefox, etc.). 2. Enter valid credentials and log in. Expected Result: Login works consistently across all browsers. Actual Result: [To be filled during execution] Priority: Medium Title: TC_FUNC_16_Mobile_Responsive_Design Scenario: Validate login page responsiveness on mobile devices. Steps to reproduce: 1. Open the login page on a mobile device. 2. Check the layout and login functionality. Expected Result: Login page is responsive and functional on mobile devices. Actual Result: [To be filled during execution] Priority: Medium Title: TC_FUNC_17_SQL_Injection_Prevention Scenario: Test SQL injection prevention in the login fields. Steps to reproduce: 1. Enter SQL injection code in the username and password fields. 2. Click on the "Login" button. Expected Result: Application prevents SQL injection. Actual Result: [To be filled during execution] Priority: High Title: TC_FUNC_18_JavaScript_Disabled Scenario: Validate login page functionality with JavaScript disabled. Steps to reproduce: 1. Disable JavaScript in the browser. 2. Attempt to log in with valid credentials. Expected Result: Application should notify that JavaScript is required. Actual Result: [To be filled during execution] Priority: Low Title: TC_FUNC_19_Cookie_Functionality Scenario: Verify cookie functionality after selecting "Remember me". Steps to reproduce: 1. Log in with "Remember me" selected. 2. Check cookies stored in the browser. Expected Result: Cookie should store user session information correctly. Actual Result: [To be filled during execution] Priority: Medium Title: TC_FUNC_20_Security_Captcha Scenario: Validate captcha functionality after multiple failed login attempts. Steps to reproduce: 1. Enter incorrect credentials multiple times. 2. Check for captcha or similar security feature. Expected Result: Captcha appears after multiple failed attempts. Actual Result: [To be filled during execution] Priority: High