@trevordsouzabrite/test-package 1.0.0

package/specs/Applicant Help Page Test Plan.md

@@ -0,0 +1,369 @@
+# Polk County Applicant Help Page Test Plan
+
+## Application Overview
+
+This plan documents automated coverage in `tests/ApplicantHelpPageTest.spec.ts` for the authenticated applicant **Help / Knowledge Base** page.
+
+The Help page is only reachable after the applicant has logged in. It is reached from the authenticated portal by clicking the **Help** link in the header navigation (which resolves to `/polkphpapplicant/s/knowledge-base`). No footer link to the Help page exists; the **Help** header link is the sole in-portal entry point.
+
+The page is a Salesforce Experience Cloud Knowledge Base component. It renders a search bar (placeholder `Search articles...`), a **Categories** sidebar filter (All, Support, Account, General), an **Article Type** sidebar filter (All, FAQ, Procedure), and a grid of article cards. Each card displays the article type badge, title, summary, publish date, and a `Read more →` action. Clicking a card navigates to the article detail page at `/polkphpapplicant/s/article?urlName=<slug>`. The detail page contains sections: Summary, Audience, Purpose, a warning block, Steps, and a **Was this article helpful?** widget with 👍 Yes / 👎 No buttons. A **← Back to Knowledge Base** button on the detail page returns the user to the list.
+
+Searching with a term that matches articles filters the card grid in place (the URL does not change — search is client-side). Searching a term with no matches shows the empty-state message `No articles found. Try a different search or category.` Clicking the category or article-type filters also updates the card list without a URL change.
+
+The expected text data for this suite is stored in `test-data/help/textContent.json`.
+
+The suite starts from the applicant dashboard, confirms the user is logged in, clicks **Help** in the header navigation, and validates the page layout, content, search, filtering, article navigation, and accessibility.
+
+## Test Scenarios
+
+### 1. Applicant Help Page Tests
+
+**Seed:** `tests/seed.spec.ts`
+
+#### 1.1. TC-01 - Authenticated Header, Footer, And Help Page H1 Are Visible
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Navigate to `/polkphpapplicant/s/?language=en_US` and wait for the **Logout** button to confirm the applicant session is authenticated.
+    - expect: The applicant portal dashboard loads and the Logout button is visible.
+  2. Click the **Help** link in the header navigation and wait for the **Knowledge Base** H1 to appear.
+    - expect: The browser navigates to the Help / Knowledge Base page.
+    - expect: The URL contains `knowledge-base`.
+    - expect: The H1 heading **Knowledge Base** is visible.
+  3. Verify all authenticated header elements.
+    - expect: The Logo image is visible.
+    - expect: The **Home** link is visible.
+    - expect: The **Create Application** link is visible.
+    - expect: The **My Applications** link is visible.
+    - expect: The **My Medical Coverage** link is visible.
+    - expect: The **Resources** link is visible.
+    - expect: The **Help** link is visible.
+    - expect: The **Privacy Policy** link is visible.
+    - expect: The **Logout** button is visible.
+  4. Scroll to the footer and verify footer elements.
+    - expect: The **Polk HealthCare Plan** footer image is visible.
+    - expect: The **CONTACT US** link is visible.
+    - expect: The **POLK HEALTHCARE PLAN FAQS** link is visible.
+    - expect: The **FIND YOUR PROVIDER** link is visible.
+    - expect: The **NOTIFY CUSTOMER SERVICE** link is visible.
+    - expect: The **ACCESSIBILITY** link is visible.
+    - expect: The **TERMS & CONDITIONS** link is visible.
+    - expect: The **PRIVACY POLICY** link is visible.
+    - expect: The copyright text **Copyright © 2026 Polk County. All Rights Reserved.** is visible.
+    
+#### 1.2. TC-02 - Knowledge Base Page Title Section Content Is Correct
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Help / Knowledge Base page and wait for the H1 heading to appear.
+    - expect: The page content area has loaded.
+  2. Locate the H1 heading and the subtitle paragraph directly beneath it.
+    - expect: The H1 heading **Knowledge Base** is visible.
+    - expect: The subtitle paragraph **Find answers to your questions** is visible directly beneath the H1.
+  3. Verify the search bar is present and has the correct placeholder text.
+    - expect: A search input with placeholder text **Search articles...** is visible.
+
+#### 1.3. TC-03 - Article List Displays The Correct Article Card Content
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Help / Knowledge Base page and wait for the article card list to load.
+    - expect: At least one article card is visible in the article grid.
+  2. Inspect the first article card in the list.
+    - expect: The article type badge **Procedure** is visible on the card.
+    - expect: The article title **How to Reset Your Password** is visible.
+    - expect: The summary text **Step-by-step guide to reset your account password quickly and securely** is visible.
+    - expect: A publish date is visible on the card (format: `4/16/2026, 5:03 AM`).
+    - expect: The **Read more →** action link text is visible on the card.
+
+#### 1.4. TC-04 - Category Filter Narrows Article List
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Help / Knowledge Base page and wait for the article list to load.
+    - expect: The Categories sidebar is visible with labels: **All**, **Support**, **Account**, **General**.
+  2. Click the **Account** category filter.
+    - expect: The article list updates to show only articles in the Account category.
+    - expect: The **How to Reset Your Password** article card remains visible.
+    - expect: The URL does not change — filtering is client-side.
+  3. Click the **Support** category filter (which shows 0 articles).
+    - expect: The article list is empty.
+    - expect: The empty-state message **No articles found. Try a different search or category.** is visible.
+  4. Click the **General** category filter (which shows 0 articles).
+    - expect: The article list is empty.
+    - expect: The empty-state message **No articles found. Try a different search or category.** is visible.
+  5. Click the **All** category filter.
+    - expect: All articles are restored to the list.
+    - expect: The **How to Reset Your Password** article card is visible again.
+
+#### 1.5. TC-05 - Article Type Filter Narrows Article List
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Help / Knowledge Base page and wait for the article list to load.
+    - expect: The Article Type sidebar is visible with labels: **All**, **FAQ**, **Procedure**.
+  2. Click the **Procedure** article type filter.
+    - expect: The article list shows only Procedure-type articles.
+    - expect: The **How to Reset Your Password** article card (tagged **Procedure**) is visible.
+    - expect: The URL does not change — filtering is client-side.
+  3. Click the **FAQ** article type filter.
+    - expect: The article list is empty because there are currently no FAQ articles.
+    - expect: The empty-state message **No articles found. Try a different search or category.** is visible.
+  4. Click the **All** article type filter.
+    - expect: All articles are restored to the list.
+    - expect: The **How to Reset Your Password** article card is visible again.
+
+#### 1.6. TC-06 - Search Box Filters Articles And Shows Empty State For No Matches
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Help / Knowledge Base page and wait for the article list to load.
+    - expect: The search box with placeholder **Search articles...** is visible and empty.
+  2. Type `password` in the search box.
+    - expect: The article list is filtered to show articles matching the term `password`.
+    - expect: The **How to Reset Your Password** article card is visible.
+    - expect: A **Clear** button appears in the search bar.
+    - expect: The URL does not change — search is client-side.
+  3. Click the **Clear** button in the search bar.
+    - expect: The search box is cleared and returns to empty.
+    - expect: The Clear button disappears.
+    - expect: The full article list is restored and the **How to Reset Your Password** card is visible.
+  4. Type `xyznotfound` in the search box (a term that matches no articles).
+    - expect: The article list is empty.
+    - expect: The empty-state message **No articles found. Try a different search or category.** is visible.
+    - expect: All category counts update to **0**.
+  5. Click the **Clear** button to reset the search.
+    - expect: The search box is cleared.
+    - expect: The full article list is restored.
+
+#### 1.7. TC-07 - Article Card Click Navigates To The Article Detail Page
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Help / Knowledge Base page and wait for the article list to load.
+    - expect: The **How to Reset Your Password** article card is visible.
+  2. Click the **How to Reset Your Password** article card.
+    - expect: The browser navigates to the article detail page.
+    - expect: The URL contains `article?urlName=how-to-reset-password`.
+    - expect: The H1 heading **How to Reset Your Password** is visible.
+    - expect: The article type badge **Procedure** is visible.
+    - expect: The metadata line shows **Published: 4/16/2026, 5:03 AM**, **Category: Account**, and **Article #: 000001013**.
+    - expect: The user remains authenticated — the Logout button is visible.
+
+#### 1.8. TC-08 - Article Detail Page Sections And Content Are Correct
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Navigate to the article detail page at `/polkphpapplicant/s/article?urlName=how-to-reset-password` and wait for the H1 to appear.
+    - expect: The article detail page loads successfully.
+  2. Verify the **Summary** section.
+    - expect: The section label **Summary** is visible.
+    - expect: The summary text **Step-by-step guide to reset your account password quickly and securely** is visible.
+  3. Verify the **Audience** section.
+    - expect: The section label **Audience** is visible.
+    - expect: The audience text contains **This article is intended for all registered customers and end users who have forgotten their password or need to reset their login credentials for security purposes.**
+  4. Verify the **Purpose** section.
+    - expect: The section label **Purpose** is visible.
+    - expect: The purpose text contains **The purpose of this procedure is to guide users through the password reset process to regain access to their account safely without contacting support.**
+  5. Verify the warning block.
+    - expect: The warning block contains **⚠️ Warning: Do not share your password reset link with anyone.**
+    - expect: The warning block contains **⚠️ The reset link expires within 24 hours of being sent.**
+    - expect: The warning block contains **⚠️ After 5 failed attempts your account will be locked.**
+  6. Verify the **Steps** section.
+    - expect: The section label **Steps** is visible.
+    - expect: **Step 1: Go to the login page and click "Forgot Password"** is visible.
+    - expect: **Step 2: Enter your registered email address and click Submit** is visible.
+    - expect: **Step 3: Check your email inbox for the password reset link** is visible.
+    - expect: **Step 4: Click the reset link within 24 hours** is visible.
+    - expect: **Step 5: Enter your new password (minimum 8 characters, must include 1 uppercase, 1 number, 1 special character)** is visible.
+    - expect: **Step 6: Confirm your new password and click Save** is visible.
+    - expect: **Step 7: Login with your new password successfully** is visible.
+
+#### 1.9. TC-09 - Was This Article Helpful Widget Is Functional
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Navigate to the article detail page at `/polkphpapplicant/s/article?urlName=how-to-reset-password` and wait for the H1 to appear.
+    - expect: The article detail page loads successfully.
+  2. Locate the **Was this article helpful?** widget at the bottom of the article.
+    - expect: The label **Was this article helpful?** is visible.
+    - expect: The **👍 Yes** button is visible.
+    - expect: The **👎 No** button is visible.
+  3. Click the **👍 Yes** button.
+    - expect: The Yes vote count increments by 1 (button label updates to **👍 Yes (1)** or higher).
+    - expect: The page does not navigate away — the user remains on the article detail page.
+    - expect: The user remains authenticated — the Logout button is visible.
+  4. Click the **👎 No** button.
+    - expect: The Yes vote count increments by 1 (button label updates to **👎 No (1)** or higher).
+    - expect: The page does not navigate away — the user remains on the article detail page.
+    - expect: The user remains authenticated — the Logout button is visible.
+  5. Click the browser refresh button.
+    - expect: The count should not be reverted back to 0.
+
+#### 1.10. TC-10 - Back To Knowledge Base Button Returns To The Knowledge Base List
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Navigate to the article detail page at `/polkphpapplicant/s/article?urlName=how-to-reset-password` and wait for the H1 to appear.
+    - expect: The article detail page loads successfully.
+  2. Click the **← Back to Knowledge Base** button.
+    - expect: The browser navigates back to the Knowledge Base list page.
+    - expect: The URL contains `knowledge-base`.
+    - expect: The H1 heading **Knowledge Base** is visible.
+    - expect: The article card list is visible.
+    - expect: The user remains authenticated — the Logout button is visible.
+
+#### 1.11. TC-11 - Browser Tab Title Is Knowledge Base
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Help / Knowledge Base page and wait for the H1 heading to appear.
+    - expect: The page has loaded.
+  2. Read `document.title` from the browser.
+    - expect: The browser tab title (`document.title`) is **Knowledge Base**.
+
+#### 1.12. TC-12 - Heading Hierarchy And Accessibility Attributes Are Correct
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Help / Knowledge Base page and wait for the H1 heading to appear.
+    - expect: The page has loaded.
+  2. Inspect the heading hierarchy on the page (traversing shadow DOM).
+    - expect: There is exactly one H1 element with the text **Knowledge Base**.
+    - expect: There are zero H2 elements on the page.
+    - expect: There are zero H3 elements on the page.
+    - expect: The H1 is the highest-level heading in the document.
+  3. Verify the HTML `lang` attribute on the root `<html>` element.
+    - expect: The document `lang` attribute is **en-US**.
+  4. Verify the Logo image in the header has a meaningful `alt` attribute.
+    - expect: The header Logo image has `alt` text **Logo**.
+
+#### 1.13. TC-13 - Help Page Is Reachable Via The Help Header Link From The Dashboard
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Navigate to `/polkphpapplicant/s/?language=en_US` and confirm the Logout button is visible.
+    - expect: The authenticated applicant dashboard loads and the Logout button is visible.
+  2. Locate the **Help** link in the header navigation bar.
+    - expect: The **Help** link is visible in the header navigation.
+    - expect: The **Help** link `href` resolves to `/polkphpapplicant/s/knowledge-base`.
+  3. Click the **Help** link.
+    - expect: The browser navigates to the Knowledge Base page.
+    - expect: The URL contains `knowledge-base`.
+    - expect: The H1 heading **Knowledge Base** is visible.
+    - expect: The Logout button is still visible, confirming the user remains authenticated.
+
+#### 1.14. TC-14 - Help Page Is Reachable Via The Help Header Link From The Resources Page
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Navigate to the authenticated Resources page at `/polkphpapplicant/s/resourcespage` and wait for the **Resources** heading to appear.
+    - expect: The Resources page loads successfully while the user remains authenticated (Logout button visible).
+  2. Click the **Help** link in the header navigation.
+    - expect: The browser navigates to the Knowledge Base page.
+    - expect: The URL contains `knowledge-base`.
+    - expect: The H1 heading **Knowledge Base** is visible.
+    - expect: The Logout button is still visible, confirming the user remains authenticated.
+
+#### 1.15. TC-15 - Header Nav Links From Help Page Return To Dashboard While Authenticated
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Help / Knowledge Base page and wait for the H1 heading to appear.
+    - expect: The Knowledge Base page loads successfully.
+  2. Click the **Home** link in the header navigation.
+    - expect: The browser navigates to the dashboard page.
+    - expect: The URL contains `/polkphpapplicant/s/` and does not contain `knowledge-base`.
+    - expect: The **Welcome to the Polk HealthCare Plan Applicant Portal** heading is visible.
+    - expect: The **Logout** button is still visible, confirming the user remains authenticated.
+  3. Navigate back to the Help / Knowledge Base page and click the Logo image in the header.
+    - expect: The browser navigates to the dashboard page.
+    - expect: The URL contains `/polkphpapplicant/s/` and does not contain `knowledge-base`.
+    - expect: The user remains authenticated.
+
+#### 1.16. TC-16 - Desktop Viewport Layout (1500x730) Renders Correctly
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Set the viewport to 1500x730 (the default Chromium project viewport defined in `playwright.config.ts`) and navigate to the Knowledge Base page.
+    - expect: The page loads without horizontal scrollbars.
+    - expect: The header, main content area, and footer are all visible.
+  2. Verify the vertical stacking order of page sections.
+    - expect: The authenticated header (Logo + nav links + Logout) appears at the top.
+    - expect: The H1 **Knowledge Base** and subtitle **Find answers to your questions** appear below the header.
+    - expect: The search bar appears below the page title.
+    - expect: The Categories and Article Type filters appear in the left sidebar.
+    - expect: The article card grid appears to the right of the filters.
+    - expect: The footer (Polk HealthCare Plan image, address block, nav links, copyright) appears at the bottom.
+    - expect: No content is clipped or overflowing horizontally.
+
+#### 1.17. TC-17 - Mobile Viewport Layout (Pixel 4a 412x732) Renders Correctly
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Set the viewport to 412x732 (matching the `Device` project — Pixel 4a (5G) — defined in `playwright.config.ts`) and navigate to the Knowledge Base page.
+    - expect: The page loads without a horizontal scrollbar.
+    - expect: The H1 heading **Knowledge Base** is visible.
+    - expect: The Logo image in the header is visible.
+    - expect: The **Logout** button is visible.
+    - expect: The search bar is visible.
+  2. Scroll to the footer on the mobile viewport.
+    - expect: The footer content — Polk HealthCare Plan image, address block, nav links, and copyright text — is visible and not broken or clipped.
+
+#### 1.18. TC-18 - No Broken Images On The Knowledge Base Page
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Help / Knowledge Base page and wait for the H1 heading to appear.
+    - expect: The page has loaded.
+  2. Check that the header Logo image has loaded correctly.
+    - expect: The Logo image (`alt="Logo"`) is visible in the header.
+    - expect: The image `naturalWidth` is greater than 0, confirming it has rendered.
+  3. Scroll to the footer and check that the Polk HealthCare Plan footer image has loaded correctly.
+    - expect: The Polk HealthCare Plan footer image (`alt="Polk HealthCare Plan"`) is visible.
+    - expect: The image `naturalWidth` is greater than 0, confirming it has rendered.
+
+#### 1.19. TC-19 - No Broken Images On The Article Detail Page
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Navigate to the article detail page at `/polkphpapplicant/s/article?urlName=how-to-reset-password` and wait for the H1 to appear.
+    - expect: The article detail page has loaded.
+  2. Check that the header Logo image has loaded correctly.
+    - expect: The Logo image (`alt="Logo"`) is visible in the header.
+    - expect: The image `naturalWidth` is greater than 0, confirming it has rendered.
+  3. Check that the article banner image has loaded correctly.
+    - expect: The **Polk County Banner** image (`alt="Polk County Banner"`) is visible in the article content area.
+    - expect: The image `naturalWidth` is greater than 0, confirming it has rendered.
+  4. Scroll to the footer and check that the Polk HealthCare Plan footer image has loaded correctly.
+    - expect: The Polk HealthCare Plan footer image (`alt="Polk HealthCare Plan"`) is visible.
+    - expect: The image `naturalWidth` is greater than 0, confirming it has rendered.
+
+#### 1.20. TC-20 - Category Filter counts should not get changed on clicking other category
+
+**File:** `tests/ApplicantHelpPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Help / Knowledge Base page and wait for the article list to load.
+    - expect: The Categories sidebar is visible with labels: **All**, **Support**, **Account**, **General**.
+  2. Click the **Support** category filter (which shows 0 articles).
+    - expect: The count present in All filter should be updated with Support Categories Count

package/specs/Applicant Landing Page Test Plan.md

@@ -0,0 +1,42 @@
+# Polk County Applicant Landing Page Test Plan
+
+## Application Overview
+
+Validate Polk County Healthcare Plan Applicant portal landing page at https://polkcounty--polkdevnew.sandbox.my.site.com/polkphpapplicant/s/?language=en_US. Focus on page load, navigation elements, content accuracy, functional links, and accessibility flow.
+
+## Test Scenarios
+
+### 1. Landing Page Validation
+
+**Seed:** `seed.spec.ts`
+
+#### 1.1. Verify different sections of the applicant landing page
+
+**File:** `ApplicantLandingPageTest.spec.ts`
+
+**Steps:**
+  1. Navigate to landing page URL
+  2. Check the Header section of the page
+    - expect: Logo Image to be visible
+    - expect: Login Button to be visible
+  3. Check the Heading & Content section of the page
+    - expect: The Welcome Heading Text 'Welcome to the Polk HealthCare Plan Applicant Portal' should be displayed
+    - Display the Instructions text
+    - expect: The Banner should be displayed
+  4. Check the Footer section of the page
+    - expect: Footer Image to be displayed
+    - expect: Address, Number & Timing to be displayed
+    - expect: The CONTACT US, POLK HEALTHCARE PLAN FAQS , FIND YOUR PROVIDER, NOTIFY CUSTOMER SERVICE, ACCESSIBILITY, TERMS & CONDITIONS & PRIVACY POLICY to be displayed
+    - expect: The copyright text to be displayed
+
+**Expected Results:**
+- All the mentioned identifiers are displayed or not 
+
+#### 1.5. Verify accessibility attributes and WCAG baseline
+
+**File:** `ApplicantLandingPageTest.spec.ts`
+
+**Steps:**
+  1. Run Axe accessibility scan on landing page
+    - expect: No critical WCAG 2.1 AA violations for major functionality
+    - expect: Interactive elements have accessible names and focusable states

package/specs/Applicant Login Page Test Plan.md

@@ -0,0 +1,116 @@
+# Polk County Applicant Login Page Test Plan
+
+## Application Overview
+
+Validate Polk County Healthcare Plan Applicant Login page at `https://polkcounty--polkdevnew.sandbox.my.site.com/polkphpapplicant/s/?language=en_US`. The login page is the entry point for applicants to access their healthcare plan applications and information. This test plan covers authentication validation, UI elements, error handling, accessibility, and security considerations.
+
+
+---
+
+## Test Scenarios
+**File:** `ApplicantLoginPageTest.spec.ts`
+
+
+#### 1. Verify all required elements of the login page are visible
+**Steps:**
+1. Navigate to the login page.
+2. Verify URL contains /loginpage.
+3. Validate visibility of:
+   - Login message text
+   - Username label & input field
+   - Password label & input field
+   - Login button
+   - Forgot Password
+   - Self Register
+
+**Expected Results:**
+- URL contains "loginpage"
+- All UI components are displayed
+- Login text displays the correct instructional message
+
+---
+#### 2. Verify error message for blank username submission
+**Steps:**
+1. Navigate to login page
+2. Click login submit button without entering any credentials.
+
+**Expected Results:**
+- Browser returns validation message: "Please fill in this field."
+
+---
+#### 3. Verify error message for blank password submission
+**Steps:**
+1. Navigate to login page
+2. Enter a valid username.
+3. Click login submit button.
+
+**Expected Results:**
+- Browser returns validation message: "Please fill in this field." for password field
+
+---
+#### 4. Verify password field masks user input
+**Steps:**
+1. Navigate to login page
+
+**Expected Results:**
+- Password input type is "password"
+- Characters typed into the field are masked
+
+---
+#### 5. Validate error message for incorrect username
+**Steps:**
+1. Navigate to login page
+2. Enter invalid username: `testing`
+3. Enter valid password
+4. Click "Login" button
+5. Observe error message
+
+**Expected Results:**
+- Error message displayed: "Login failed. Please check your credentials and try again."
+
+---
+
+#### 6. Login with Invalid Password
+**Steps:**
+1. Navigate to login page
+2. Enter valid username
+3. Enter invalid password: `testing`
+4. Click "Login" button
+5. Observe error message
+
+**Expected Results:**
+- Error message displayed: "Login failed. Please check your credentials and try again."
+
+---
+#### 7. Login with Valid Credentials
+**Steps:**
+1. Navigate to login page
+2. Enter valid username
+3. Enter valid password
+4. Click "Login" button
+
+**Expected Results:**
+- Applicant should get logged and see the logout button
+
+---
+### 8. Verify navigation to Forgot Password
+**Steps:**
+1. From the login page, click **Forgot Password**.
+**Expected results:**
+- User is taken to the forgot-password route (URL contains e.g. `forgetpassword`); page shows forgot-password content (see `Applicant Forgot Password Page Test Plan.md`).
+
+---
+
+### 9. Verify navigation to Self Register
+**Steps:**
+1. From the login page, click **Self Register**.
+**Expected results:**
+- User reaches the self-registration flow or URL defined by the product; page loads without error.
+
+---
+
+### 10. Optional — Global chrome (header / footer) on login page
+**Steps:**
+1. On the login page, confirm header (logo, **Login** / navigation as designed) and scroll to footer.
+**Expected results:**
+- Layout is consistent with other public applicant pages; critical chrome is present and not broken on typical viewports.