@trevordsouzabrite/test-package 1.0.0

package/specs/Applicant Create Application Page Test Plan.md

@@ -0,0 +1,440 @@
+# Polk County Applicant Create Application Page Test Plan
+
+## Application Overview
+
+This plan documents the automated coverage in `tests/ApplicantCreateApplicationPageTest.spec.ts` for the applicant **Create Application** wizard. The suite starts from the applicant portal, opens the Create Application flow from the header, and validates the wizard from **Application Details** through final application submission.
+
+Tests tagged `@auth` rely on an authenticated applicant session. When `AUTH=true`, the suite saves auth state after each test through `saveAuthState(page.context())`.
+
+Test data and expected copy are sourced from:
+
+- `test-data/createApplication/formData.json`
+- `test-data/createApplication/textMessages.json`
+
+## Shared Preconditions
+
+| Step | Action | Expected Result |
+|------|--------|-----------------|
+| 1 | Navigate to `/polkphpapplicant/s/?language=en_US` | Applicant portal loads |
+| 2 | Wait for **Logout** button | Applicant session is authenticated |
+| 3 | Click **Create Application** link | Create Application flow opens |
+| 4 | Wait for **Application Details** title | Screen 1 is ready |
+
+## Screen 1 - Application Details
+
+### TC-01 - Applicant Details Elements Are Visible
+
+**Automated test:** `Verify the all the elements are visible on the Create Application page - Applicant Details @auth`
+
+**Objective:** Verify all key Application Details elements are visible.
+
+**Coverage:**
+
+- Applicant identity fields: first name, middle initial, last name, suffix, DOB, SSN, email, landline, cell phone.
+- Demographic dropdowns: primary phone type, race, ethnicity, gender, marital status, citizenship, veteran, language, insurance coverage.
+- Homeless checkbox.
+- Physical Address card and fields.
+- Mailing Address card, same-as-physical toggle, and fields.
+
+**Expected Result:** All listed labels, inputs, dropdowns, checkboxes, and address sections are visible.
+
+### TC-02 - Applicant Details Required Field Errors
+
+**Automated test:** `Verify the required elements error messages are visible on the Create Application page - Applicant Details @auth`
+
+**Objective:** Verify required validation appears when mandatory applicant details are blank.
+
+**Steps:**
+
+1. Clear first name, last name, DOB, SSN, and email.
+2. Set required demographic dropdowns to `-- No Value --`.
+3. Click **Next**.
+
+**Expected Result:** Required messages from `textMessages.json` are shown for first name, last name, DOB, SSN, email, primary phone type, race, ethnicity, gender, marital status, citizenship, veteran, language, and insurance coverage.
+
+### TC-03 - Application Details Dropdown Values
+
+**Automated test:** `Verify the dropdowns are populated with the correct values on the Application Details screen @auth`
+
+**Objective:** Verify Application Details dropdown options match configured test data.
+
+**Coverage:** Race, ethnicity, gender, marital status, citizenship, veteran, language, insurance coverage, and primary phone type.
+
+**Expected Result:** Each dropdown contains all expected options from `createApplicationFormData.dropdowns`.
+
+### TC-04 - Navigate From Application Details To Applicant Income
+
+**Automated test:** `Verify the application details are filled correctly in screen - 1 - Application Details and the user moves to the next screen - 2 - Income @auth`
+
+**Steps:**
+
+1. Fill Application Details using `fillApplicationDetails()`.
+2. Click **Next**.
+
+**Expected Result:** Applicant Income screen is displayed.
+
+## Screen 2 - Applicant Income
+
+### TC-05 - Applicant Income Elements And Required Messages
+
+**Automated test:** `Verify the all the elements & required messages are visible on the Create Application page - Applicant Income @auth`
+
+**Objective:** Verify Applicant Income screen behavior for both **Yes** and **No** income paths.
+
+**Coverage:**
+
+- Required message for unanswered **Have you received income in last 30 days?**
+- **Yes** path income source checkboxes and related amount/employer/self-employment sections.
+- Required messages for missing selected income source fields.
+- **No** path explanation fields, support/financial transaction dropdowns, public assistance checkboxes, and required messages.
+- Third-party support block appears when support is answered **Yes**.
+
+**Expected Result:** All expected sections and validation messages appear for both income paths.
+
+### TC-06 - Applicant Monthly Income Total Calculation
+
+**Automated test:** `Verify the Monthly Income Sums up to the Total Primary Applicant Income Monthly correctly @auth`
+
+**Objective:** Verify the total primary applicant monthly income equals the sum of all entered income source amounts.
+
+**Steps:**
+
+1. Complete Application Details and open Applicant Income.
+2. Select **Yes** for income.
+3. Select all income source checkboxes.
+4. Generate and enter random amounts for each amount field.
+5. Calculate the expected sum in the test.
+
+**Expected Result:** `Total Primary Applicant Income Monthly` equals the calculated sum.
+
+### TC-07 - Navigate From Applicant Income To Household Members
+
+**Automated test:** `Verify the application details are filled correctly in screen - 1 & 2 - Application Details & Income and the user moves to the next screen - 3 - Household Members @auth`
+
+**Steps:**
+
+1. Complete Application Details.
+2. Complete Applicant Income through `fillApplicantIncomeScreenRandomly()`.
+
+**Expected Result:** Household Members screen is displayed.
+
+## Screen 3 - Household Members
+
+### TC-08 - Household Members Elements Are Visible
+
+**Automated test:** `Verify all the elements are visible on the Create Application page - Household Members @auth`
+
+**Objective:** Verify Household Members screen summary controls and actions.
+
+**Expected Result:** Household hint, Edit button, Add Household Member button, total household count, total monthly household income, and FPL percentage elements are visible.
+
+### TC-09 - Edit Primary Applicant Details And Income Parity
+
+**Automated test:** `Verify all the elements are visible on the Create Application page - Household Members - Edit Primary Applicant & also verify the income amounts entered in the screen 2 is displayed correctly in the Edit Screen @auth @knownissue`
+
+**Objective:** Verify primary applicant details and Applicant Income amounts carry into the Edit Primary Applicant view.
+
+**Coverage:**
+
+- Primary applicant demographic fields are visible and populated.
+- Relationship is **Self**.
+- Seeking benefits is **Yes**.
+- Income total matches the sum of Applicant Income line items.
+- Each selected Applicant Income source amount matches the corresponding Edit Primary Applicant amount.
+
+**Expected Result:** Demographic values are present and parsed income amounts match Screen 2 entries.
+
+**Known Issue:** Test is tagged `@knownissue`; comments note missing/incorrect field labeling for First Employer Gross Monthly Income in the edit screen.
+
+### TC-10 - Add Household Member Elements And Income Branches
+
+**Automated test:** `Verify all the elements are visible on the Create Application page - Household Members - Add Household Member @auth @knownissue`
+
+**Objective:** Verify the Add Household Member form defaults and income/no-income branches.
+
+**Coverage:**
+
+- New household member fields are visible and initially empty.
+- Gender and marital status default to **Select an Option**.
+- Seeking benefits defaults to **Yes**.
+- **Has income = Yes** displays income source controls and amount fields.
+- **Has income = No** displays no-income explanation/support/public assistance sections.
+
+**Expected Result:** Add member form and both income branches render expected controls.
+
+**Known Issue:** Test is tagged `@knownissue`; comments note missing/incorrect field labeling for First Employer Gross Monthly Income.
+
+### TC-11 - Household Total Matches Applicant Income
+
+**Automated test:** `Verify the total monthly household income is getting displayed correctly in the Household Members screen @auth @knownissue`
+
+**Objective:** Verify Household Members total monthly income includes the applicant income total.
+
+**Steps:**
+
+1. Complete Applicant Income with **Yes** and `incomeSourceCount: 3`.
+2. Read Household Members total monthly income.
+
+**Expected Result:** Household total contains the Applicant Income total.
+
+**Known Issue:** Test is tagged `@knownissue`.
+
+### TC-12 - Household Total After Adding New Member
+
+**Automated test:** `Verify the total monthly household income is getting displayed correctly in the Household Members screen after a new household member is added @auth @knownissue`
+
+**Objective:** Verify household total updates after adding a new household member with income.
+
+**Steps:**
+
+1. Complete Applicant Income with three sources.
+2. Add a household member using `addHouseholdMember()`.
+3. Sum applicant income and new member income.
+
+**Expected Result:** Displayed household total equals the computed sum.
+
+**Known Issue:** Test is tagged `@knownissue`.
+
+### TC-13 - Edit Household Member Income Total
+
+**Automated test:** `Verify the user is able to edit the household member details and the total monthly household income is getting displayed correctly in the Household Members screen @auth`
+
+**Objective:** Verify editing the primary applicant income from the household edit screen updates total monthly household income.
+
+**Steps:**
+
+1. Complete Applicant Income with three sources.
+2. Open **Edit**.
+3. Add one additional income source not already selected.
+4. Compare displayed total against applicant income plus edited income amount.
+
+**Expected Result:** Household total equals the expected edited sum.
+
+## Screen 4 - Document Upload
+
+### TC-14 - Navigate To Document Upload
+
+**Automated test:** `Verify the application details are filled correctly in screen - 1, 2 & 3 - Application Details & Income and the user moves to the next screen - 4 - Document Upload @auth`
+
+**Objective:** Verify the wizard advances from Household Members to Document Upload.
+
+**Expected Result:** Document Upload screen title is visible.
+
+### TC-15 - Document Upload Elements Are Visible
+
+**Automated test:** `Verify the elements are visible on the Document Upload screen @auth`
+
+**Objective:** Verify Document Upload instructions, member document block, and income-source upload controls.
+
+**Expected Result:** Notification, instructions, member document block, member name, and each required upload input for selected income sources are visible.
+
+### TC-16 - Upload Required Documents
+
+**Automated test:** `Verify the files are getting uploaded or not on the Document Upload screen @auth`
+
+**Objective:** Verify files can be uploaded for selected income source documents and optional identification card.
+
+**Steps:**
+
+1. Complete prior screens with selected income sources.
+2. Upload identification card if present.
+3. Upload `test-data/Sample.png` for each selected income source document.
+4. Verify uploaded documents table.
+
+**Expected Result:** Uploaded Documents section is visible and document names match expected references.
+
+### TC-17 - View Or Delete Uploaded Document
+
+**Automated test:** `Verify the user is able to view or delete the uploaded document on the Document Upload screen @auth`
+
+**Status:** Skipped with `test.skip`.
+
+**Objective:** Intended to verify view/download and delete confirmation behavior for an uploaded document.
+
+**Expected Result:** When enabled, View downloads a file containing `Sample` in the suggested filename, Cancel keeps the document, and OK removes it.
+
+**Skip Reason:** Comment states the delete pop-up is not getting displayed.
+
+## Screen 5 - Enrollment Acknowledgement
+
+### TC-18 - Navigate To Enrollment Acknowledgement
+
+**Automated test:** `Verify the application details are filled correctly in screen - 1, 2, 3 & 4 - the user moves to the next screen - 5 - Enrollment Acknowledgement @auth`
+
+**Objective:** Verify the wizard advances from Document Upload to Enrollment Acknowledgement.
+
+**Expected Result:** Enrollment Acknowledgement block is visible.
+
+### TC-19 - Enrollment Acknowledgement Elements And Copy
+
+**Automated test:** `Verify the elements are visible on the Enrollment Acknowledgement screen @auth`
+
+**Objective:** Verify Enrollment Acknowledgement content and handbook link.
+
+**Coverage:**
+
+- Title and text blocks are visible.
+- Text blocks match configured form data.
+- Member handbook link is visible and points to the expected Polk Healthcare Plan URL.
+- Acknowledgement checkbox/text block is visible.
+
+**Expected Result:** All Enrollment Acknowledgement UI and configured copy validations pass.
+
+## Screen 6 - Additional Information & Attestation
+
+### TC-20 - Navigate To Additional Information & Attestation
+
+**Automated test:** `Verify the application details are filled correctly in screen - 1, 2, 3, 4 & 5- the user moves to the next screen - 6 - Additional Information & Attestation @auth`
+
+**Objective:** Verify the wizard advances from Enrollment Acknowledgement to Additional Information & Attestation.
+
+**Expected Result:** Additional Information block is visible.
+
+### TC-21 - Additional Information & Attestation Elements
+
+**Automated test:** `Verify the elements are visible on the Additional Information & Attestation screen @auth`
+
+**Objective:** Verify provider selection, contact preferences, preview application, attestation, date, and disclaimer.
+
+**Coverage:**
+
+- Primary care provider dropdown.
+- Application mode of updates checkboxes.
+- Plan mode of updates checkboxes and no-contact option.
+- SMS privacy disclosure.
+- Preview Application link opens a popup with a visible iframe.
+- Certification label, legal name textbox, today's date, and disclaimer.
+
+**Expected Result:** All listed controls are visible and today's date matches the expected `DD-MM-YYYY` format.
+
+## Screen 7 - Sign Consent Form
+
+### TC-22 - Navigate To Sign Consent Form
+
+**Automated test:** `Verify the application details are filled correctly in screen - 1, 2, 3, 4, 5 & 6- the user moves to the next screen - 7 - Sign Consent Form @auth`
+
+**Objective:** Verify the wizard advances from Additional Information & Attestation to Sign Consent Form.
+
+**Expected Result:** Sign Consent Form title is visible.
+
+### TC-23 - Sign Consent Form Elements
+
+**Automated test:** `Verify the elements are visible on the Sign Consent Form screen @auth`
+
+**Objective:** Verify consent form UI for both available states.
+
+**Coverage:**
+
+- If the consent form is visible: header, name/information block, use/disclosure block, consent checkbox, signature canvas, hint, Accept Signature, Clear, and Agree and Consent buttons.
+- If consent was already submitted: already-submitted block and Submit Application button.
+
+**Expected Result:** Correct consent form state is visible.
+
+### TC-24 - Clear And Sign Consent Form
+
+**Automated test:** `Verify the user clears and signs the consent form @auth`
+
+**Objective:** Verify signature drawing, clearing, re-signing, accepting, consenting, and submitting.
+
+**Steps:**
+
+1. Select consent information checkbox.
+2. Draw signature.
+3. Click **Clear** and verify canvas is empty.
+4. Draw signature again and verify canvas is not empty.
+5. Accept signature and agree/consent.
+6. Submit application.
+
+**Expected Result:** Signature canvas state changes correctly, thank-you block appears, and Submit Application button is available.
+
+**Conditional Behavior:** Test skips itself if the consent form was already submitted.
+
+## Screen 8 - Social Services Assessment
+
+### TC-25 - Navigate To Social Services Assessment
+
+**Automated test:** `Verify the application details are filled correctly in screen - 1, 2, 3, 4, 5, 6 & 7 - the user moves to the next screen - 8 - Social Services Assessment @auth`
+
+**Objective:** Verify the wizard advances from Sign Consent Form to Social Services Assessment.
+
+**Expected Result:** Client Needs Assessment block is visible.
+
+### TC-26 - Social Services Assessment Elements
+
+**Automated test:** `Verify the elements are visible on the Social Services Assessment screen @auth`
+
+**Objective:** Verify assessment choice behavior.
+
+**Steps:**
+
+1. Verify **I choose** and **I decline** radio buttons.
+2. Select **I choose to complete the assessment**.
+3. Verify Housing, Environment, Substance Abuse, Mental Health, and Disability sections/dropdowns.
+4. Select **I decline to complete the assessment**.
+
+**Expected Result:** Assessment sections appear when choosing to complete and are hidden after declining.
+
+### TC-27 - Social Services Assessment Dropdown Values
+
+**Automated test:** `Verify the dropdown values are populated with the correct values on the Social Services Assessment screen @auth`
+
+**Objective:** Verify Social Services Assessment dropdown options match configured test data.
+
+**Coverage:** Housing, Environment, Substance Abuse, Mental Health, Disability Question 1, and Disability Question 2 dropdowns.
+
+**Expected Result:** Each dropdown contains all expected values from `createApplicationFormData.dropdowns`.
+
+### TC-28 - Submit Application And Validate Success
+
+**Automated test:** `Verify the user is able to submit the application and get a success message @auth`
+
+**Objective:** Verify final application submission path.
+
+**Steps:**
+
+1. Complete screens 1 through 7.
+2. Open Social Services Assessment.
+3. Select **I decline to complete the assessment**.
+4. Click **Submit Assesment**.
+
+**Expected Result:** Thank-you message is visible after submission.
+
+## Traceability
+
+| TC | Automated Test Summary | Tags / Status |
+|----|------------------------|---------------|
+| TC-01 | Applicant Details elements visible | `@auth` |
+| TC-02 | Applicant Details required errors | `@auth` |
+| TC-03 | Application Details dropdown values | `@auth` |
+| TC-04 | Navigate Screen 1 to Screen 2 | `@auth` |
+| TC-05 | Applicant Income elements and validation | `@auth` |
+| TC-06 | Applicant monthly income sum | `@auth` |
+| TC-07 | Navigate Screen 2 to Screen 3 | `@auth` |
+| TC-08 | Household Members elements visible | `@auth` |
+| TC-09 | Edit Primary Applicant income parity | `@auth @knownissue` |
+| TC-10 | Add Household Member branches | `@auth @knownissue` |
+| TC-11 | Household total matches applicant income | `@auth @knownissue` |
+| TC-12 | Household total after adding member | `@auth @knownissue` |
+| TC-13 | Edit household member income total | `@auth` |
+| TC-14 | Navigate to Document Upload | `@auth` |
+| TC-15 | Document Upload elements visible | `@auth` |
+| TC-16 | Upload required documents | `@auth` |
+| TC-17 | View or delete uploaded document | `@auth`, skipped |
+| TC-18 | Navigate to Enrollment Acknowledgement | `@auth` |
+| TC-19 | Enrollment Acknowledgement elements/copy | `@auth` |
+| TC-20 | Navigate to Additional Information | `@auth` |
+| TC-21 | Additional Information elements | `@auth` |
+| TC-22 | Navigate to Sign Consent Form | `@auth` |
+| TC-23 | Sign Consent Form elements | `@auth` |
+| TC-24 | Clear and sign consent form | `@auth`, conditional skip |
+| TC-25 | Navigate to Social Services Assessment | `@auth` |
+| TC-26 | Social Services Assessment elements | `@auth` |
+| TC-27 | Social Services dropdown values | `@auth` |
+| TC-28 | Submit application success | `@auth` |
+
+## Notes
+
+- Several tests use `test.setTimeout(0)` because they cover long end-to-end wizard flows.
+- Document upload tests use `test-data/Sample.png`.
+- Some tests intentionally use random income source selection and random generated amounts, then assert against values returned by page object helper methods.
+- The skipped document view/delete test should be re-enabled once the delete confirmation modal is available.

package/specs/Applicant Dashboard Page Test Plan.md

@@ -0,0 +1,74 @@
+# Polk County Applicant Dashboard Page Test Plan
+
+## Application Overview
+
+Validate Polk County Healthcare Plan Applicant portal Dashboard Page after the user has successfully logged in 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. Verify different sections of the applicant landing page
+
+**File:** `ApplicantDashboardPageTest.spec.ts`
+
+**Steps:**
+  1. Navigate to landing page URL
+  2. Check the Header section of the page
+    - expect: Logo Image to be visible
+    - expect: Home Link, Create Application Link, My Application Link, My Medical Coverage Link, Resources Link
+    - expect: Logout 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 
+
+--- 
+
+#### 2. Verify Navigation of Create Application Page
+**Steps:**
+1. From the Dashboard page, click **Create Application link**.
+**Expected results:**
+- User reaches the create application or URL defined by the product; page loads without error.
+
+---
+
+
+#### 3. Verify Navigation of My Application Page
+**Steps:**
+1. From the Dashboard page, click **Create Application link**.
+**Expected results:**
+- User reaches the create application or URL defined by the product; page loads without error.
+
+---
+
+#### 4. Verify Navigation of My Medical Coverage Page
+**Steps:**
+1. From the Dashboard page, click **Create Application link**.
+**Expected results:**
+- User reaches the create application or URL defined by the product; page loads without error.
+
+---
+
+#### 5. Verify Navigation of Resources Page
+**Steps:**
+1. From the Dashboard page, click **Create Application link**.
+**Expected results:**
+- User reaches the create application or URL defined by the product; page loads without error.
+
+---
+
+
+#### 1.5. Verify accessibility attributes and WCAG baseline
+
+
+**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 Forgot Password Page Test Plan.md

@@ -0,0 +1,112 @@
+# Polk County Applicant Forgot Password Page Test Plan
+
+## Application Overview
+
+Validate Polk County Healthcare Plan Applicant Forgot Password page
+
+---
+
+## Test Scenarios
+**File:** `ApplicantForgotPasswordPageTest.spec.ts`
+
+Pre-Condition.
+1. User will be redirected to the URL /polkphpapplicant/s/?language=en_US
+2. User will click on Login Button on the header
+3. User will click on Forgot Password Link in Login Page
+4. User will be on the Forgot Password Page.
+
+
+#### 1. Verify the applicant is redirected to the forgot password page
+**Steps:**
+1. Validate the URL is correct with 'polkphpapplicant/s/forgetpassword'
+2. Validate visibility of:
+   - Forgot Password Title
+   - Forgot Password Message
+   - Forgot Password Field Name & Input Field
+   - Send Reset Link Button
+
+**Expected Results:**
+- URL contains "forgetpassword"
+- All UI components are displayed
+
+---
+#### 2. Verify when the forgot password input field is left blank the submit button is disabled
+**Steps:**
+1. The Forgot Password Input Field should be left blank
+2. Check the Button is disabled
+
+**Expected Results:**
+- Send Reset Link Button should be disabled
+
+---
+#### 3. Verify when the forgot password input field is not empty with valid input the submit button is enabled & success message should be displayed on submission
+**Steps:**
+1. Enter the Forgot Password Field with testuser@gmail.com
+2. Validate Field Not Empty
+3. Validate Send Reset Link Button is enabled
+4. Click Send Reset Link Button.
+5. Validate the success to be displayed and success message text
+
+**Expected Results:**
+- Returns field is not empty, Send Reset Link Button is enabled
+- Success Message "If an account exists for this email/username, a reset link has been sent." is displayed
+
+---
+#### 4. Verify when invalid email format is entered, error message should be displayed
+**Steps:**
+1. Enter email as testuser
+2. Click Send Reset Link Button
+
+**Expected Results:**
+- The error message "Enter a valid email address, such as name@email.com." should be displayed
+
+---
+#### 5. Verify the success message is not shown before submit
+**Steps:**
+1. Enter a valid email in the field but do **not** click **Send reset link**
+2. Observe the area where success feedback appears (e.g. success banner / message region)
+
+**Expected Results:**
+- No success message is displayed prior to submission
+
+---
+#### 6. Verify clearing the field after valid input disables the submit button again
+**Steps:**
+1. Reach the Forgot Password page
+2. Enter a valid email (e.g. `testuser@gmail.com`)
+3. Confirm **Send reset link** is enabled
+4. Clear the Email / Username field completely
+5. Check the button state
+
+**Expected Results:**
+- After the field is empty again, **Send reset link** is disabled (consistent with scenario 2 in the main plan)
+
+---
+#### 7. Verify invalid email error clears after correcting input and submitting successfully
+**Steps:**
+1. Enter an invalid value (e.g. `testuser`) and click **Send reset link**
+2. Confirm the validation error is shown
+3. Replace the value with a valid email (e.g. `testuser@gmail.com`)
+4. Click **Send reset link**
+
+**Expected Results:**
+- Validation error is no longer shown (or field is no longer in error state) after correction
+- Success message matches main plan scenario 3: "If an account exists for this email/username, a reset link has been sent."
+
+---
+#### 8. Verify whitespace-only input does not submit a reset as valid email
+**Steps:**
+1. Leave the field empty or enter only spaces (e.g. `   `)
+2. If the button is enabled, click **Send reset link**; if disabled, note behavior
+
+**Expected Results:**
+- Either **Send reset link** remains disabled until non-whitespace input is entered, **or** validation prevents submission and an appropriate message is shown (align with product rules)
+
+#### 9. Verify global chrome (header and footer) on the forgot password page
+**Steps:**
+1. Reach the Forgot Password page (Pre-Condition A or B)
+2. Confirm presence of key portal chrome (e.g. logo/header area, primary navigation or login entry point as designed)
+3. Scroll to the footer and confirm expected footer links or copyright text (per design system)
+
+**Expected Results:**
+- Page layout is consistent with other public applicant pages; no broken layout or missing critical navigation/footer elements