@trevordsouzabrite/test-package 1.0.0

package/specs/Applicant Privacy Policy Page Test Plan.md

@@ -0,0 +1,196 @@
+# Polk County Applicant Privacy Policy Page Test Plan
+
+## Application Overview
+
+This plan documents automated coverage in `tests/ApplicantPrivacyPolicyPageTest.spec.ts` for the authenticated applicant **Privacy Policy** page.
+
+The Privacy Policy page is only reachable after the applicant has logged in. It is reached from the authenticated portal by clicking the **Privacy Policy** link in the header navigation (which resolves to `/polkphpapplicant/s/privacy-policy`). The footer also contains a **PRIVACY POLICY** link; in the authenticated portal that link resolves to `#` on the current page rather than navigating away, so the primary navigation entry point is the header link.
+
+The suite starts from the applicant dashboard, confirms that the user is logged in, clicks **Privacy Policy** in the header navigation, and validates the page layout, content, and navigation behaviour.
+
+## Test Scenarios
+
+### 1. Applicant Privacy Policy Page Tests
+
+**Seed:** `tests/seed.spec.ts`
+
+#### 1.1. TC-01 - Authenticated Header, Footer, And Privacy Policy H1 Are Visible
+
+**File:** `tests/ApplicantPrivacyPolicyPageTest.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 **Privacy Policy** link in the header navigation and wait for the **Polk County Privacy Policy** H1 to appear.
+    - expect: The browser navigates to the Privacy Policy page.
+    - expect: The URL contains `privacy-policy`.
+    - expect: The H1 heading **Polk County Privacy Policy** 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 © 2025 Polk County. All Rights Reserved.** is visible.
+
+#### 1.2. TC-02 - Registration Information Section Content Is Correct
+
+**File:** `tests/ApplicantPrivacyPolicyPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Privacy Policy page and wait for the H1 heading to appear.
+    - expect: The page content area has loaded.
+  2. Locate the **Registration Information** H2 heading.
+    - expect: The H2 heading **Registration Information** is visible on the page.
+  3. Read the first paragraph under **Registration Information**.
+    - expect: The paragraph contains the text: *We require some basic information at the time of account creation. When you create your own username and password, we ask you for a valid email address. The Website or Service may also request your phone number for receiving SMS/MMS messages.*
+  4. Locate and read the SMS Privacy Notice paragraph.
+    - expect: The paragraph contains the bold label **SMS Privacy Notice:**
+    - expect: The paragraph contains the text: *Mobile information will not be shared with third parties or affiliates for marketing or promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.*
+
+#### 1.3. TC-03 - How Polk County Uses Your Information Section Content Is Correct
+
+**File:** `tests/ApplicantPrivacyPolicyPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Privacy Policy page and wait for the H1 heading to appear.
+    - expect: The page content area has loaded.
+  2. Locate the **How Polk County Uses Your Information** H2 heading.
+    - expect: The H2 heading **How Polk County Uses Your Information** is visible on the page.
+  3. Locate the introductory paragraph under the H2.
+    - expect: The paragraph contains the text: *We may use your information for the following purposes:*
+  4. Verify the bulleted list of data-use items is present and contains exactly 9 items.
+    - expect: The list contains exactly 9 items.
+    - expect: Item 1: *We use your Registration Information to create your account and provide you the Service.*
+    - expect: Item 2: *We use your User Personal Information, specifically your username, to identify you on the Service.*
+    - expect: Item 3: *We use your Profile Information to fill out your account profile and to share that profile with other users.*
+    - expect: Item 4: *We use your email address and phone number to communicate with you.*
+    - expect: Item 5: *We use User Personal Information to respond to support requests.*
+    - expect: Item 6 mentions surveys, beta programs, and consent.
+    - expect: Item 7: *We use Usage Information and Device Information to better understand how our users use the Service and to make improvements.*
+    - expect: Item 8 mentions security purposes and fraud.
+    - expect: Item 9 mentions legal obligations and Terms of Service.
+  5. Locate and read the closing paragraph of the section.
+    - expect: The paragraph contains the text: *We limit our use of your User Personal Information to the purposes listed in this Privacy Policy. If we need to use your User Personal Information for other purposes, we will ask for your permission first. You can always see what information we have, how we are using it, and what permissions you have given us.*
+
+#### 1.4. TC-04 - Browser Tab Title Is Privacy Policy
+
+**File:** `tests/ApplicantPrivacyPolicyPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Privacy Policy 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 **Privacy Policy**.
+
+#### 1.5. TC-05 - Heading Hierarchy And Accessibility Attributes Are Correct
+
+**File:** `tests/ApplicantPrivacyPolicyPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Privacy Policy page and wait for the H1 heading to appear.
+    - expect: The page has loaded.
+  2. Inspect the heading hierarchy on the page.
+    - expect: There is exactly one H1 element with the text **Polk County Privacy Policy**.
+    - expect: There are exactly two H2 elements: **Registration Information** and **How Polk County Uses Your Information**.
+    - expect: No H3 or lower-level headings are present.
+    - expect: Headings appear in correct document order: H1 before both H2 elements.
+  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.6. TC-06 - PRIVACY POLICY Link On Another Authenticated Page Navigates To Privacy Policy
+
+**File:** `tests/ApplicantPrivacyPolicyPageTest.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. Scroll to the footer and click the **PRIVACY POLICY** link in the header navigation.
+    - expect: The browser navigates to the Privacy Policy page.
+    - expect: The URL contains `privacy-policy`.
+    - expect: The H1 heading **Polk County Privacy Policy** is visible.
+    - expect: The Logout button is still visible, confirming the user remains authenticated.
+
+#### 1.7. TC-07 - Header Nav Links From Privacy Policy Page Return To Dashboard While Authenticated
+
+**File:** `tests/ApplicantPrivacyPolicyPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Privacy Policy page and wait for the H1 heading to appear.
+    - expect: The Privacy Policy 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 `privacy-policy`.
+    - 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 Privacy Policy 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 `privacy-policy`.
+    - expect: The user remains authenticated.
+
+#### 1.8. TC-08 - Desktop Viewport Layout (1500x730) Renders Correctly
+
+**File:** `tests/ApplicantPrivacyPolicyPageTest.spec.ts`
+
+**Steps:**
+  1. Set the viewport to 1500x730 (the default Chromium project viewport defined in `playwright.config.ts`) and navigate to the Privacy Policy page.
+    - expect: The page loads without horizontal scrollbars.
+    - expect: The header, main content, 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 main content area (**Polk County Privacy Policy** H1, both H2 sections, paragraphs, and list) appears below the header.
+    - 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.9. TC-09 - Mobile Viewport Layout (Pixel 4a 412x732) Renders Correctly
+
+**File:** `tests/ApplicantPrivacyPolicyPageTest.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 Privacy Policy page.
+    - expect: The page loads without a horizontal scrollbar.
+    - expect: The H1 heading **Polk County Privacy Policy** is visible.
+    - expect: The Logo image in the header is visible.
+    - expect: The **Logout** button 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.10. TC-10 - SMS Privacy Notice Bold Lead-In Formatting Is Present
+
+**File:** `tests/ApplicantPrivacyPolicyPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Privacy Policy page and wait for the H1 heading to appear.
+    - expect: The page has loaded.
+  2. Locate the SMS Privacy Notice paragraph and inspect the **SMS Privacy Notice:** lead-in label.
+    - expect: The text **SMS Privacy Notice:** is rendered inside a `<strong>` element.
+    - expect: The label is visually distinct (bold) from the surrounding paragraph text.
+
+#### 1.11. TC-11 - No Broken Images On The Privacy Policy Page
+
+**File:** `tests/ApplicantPrivacyPolicyPageTest.spec.ts`
+
+**Steps:**
+  1. Open the Privacy Policy 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.

package/specs/Applicant Resources Page Test Plan.md

@@ -0,0 +1,107 @@
+# Polk County Applicant Resources Page Test Plan
+
+## Application Overview
+
+This plan documents automated coverage in `tests/ApplicantResourcesPageTest.spec.ts` for the authenticated applicant **Resources** page.
+
+The suite starts from the applicant dashboard, confirms that the user is logged in, opens the **Resources** page from the authenticated header, and validates the page layout plus resource document links.
+
+## 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 **Resources** link in the header | Resources page opens |
+| 4 | Wait for **Resources** title | Resources page is ready |
+
+## Test Scenarios
+
+### TC-01 - Header, Footer, And Resources Title Are Visible
+
+**Automated test:** `Verify the header & footer sections are visible on the resources page @auth`
+
+**Objective:** Verify the authenticated Resources page renders the shared portal header, shared footer, and Resources page title.
+
+**Steps:**
+
+1. Open the Resources page after login.
+2. Verify authenticated header elements.
+3. Scroll to the footer.
+4. Verify footer elements.
+5. Verify the Resources page title.
+
+**Expected Result:**
+
+- Logo is visible.
+- Header links are visible: **Home**, **Create Application**, **My Application**, **My Medical Coverage**, and **Resources**.
+- **Logout** button is visible.
+- Footer image is visible.
+- Footer links are visible: **CONTACT US**, **POLK HEALTHCARE PLAN FAQS**, **FIND YOUR PROVIDER**, **NOTIFY CUSTOMER SERVICE**, **ACCESSIBILITY**, **TERMS & CONDITIONS**, and **PRIVACY POLICY**.
+- Copyright text is visible.
+- **Resources** title is visible.
+
+### TC-02 - Resource Document Links Are Visible
+
+**Automated test:** `Verify the resources page elements are visible @auth`
+
+**Objective:** Verify all expected document links are displayed on the Resources page.
+
+**Expected Resource Links:**
+
+- `Polk HealthCare Plan Member Handbook (English).pdf`
+- `UNIVERSAL HOUSEHOLD AUTHORIZATION FORM_LIMITED_UPDATED 11.18.25.docx`
+- `UNIVERSAL SHARED DATA INFORMATION SYSTEM_Updated 11.18.25.docx`
+- `Eligibility - Income Verification Statement 031925.pdf`
+- `Third Party Support.pdf`
+
+**Expected Result:** All five resource document links are visible.
+
+### TC-03 - Resource Links Open Successfully In New Tabs
+
+**Automated test:** `Verify the links open successfully in a new tab @auth`
+
+**Objective:** Verify each resource link opens in a new tab and returns a successful document response.
+
+**Steps:**
+
+1. Read the `href` for the **Polk HealthCare Plan Member Handbook** link.
+2. Click the link and wait for a new browser tab.
+3. Wait for the new tab to load.
+4. Send an API request to the link `href`.
+5. Verify response status and content type.
+6. Verify the new tab URL contains the same `href`.
+7. Close the new tab.
+8. Repeat the same validation for the remaining resource links.
+
+**Expected Result For Each Resource Link:**
+
+- A new tab opens after clicking the link.
+- The new tab finishes loading.
+- The request to the link returns HTTP status `200`.
+- Response `content-type` contains `application/pdf`.
+- New tab URL contains the link `href`.
+- New tab closes successfully before the next link is tested.
+
+**Covered Links:**
+
+- Polk HealthCare Plan Member Handbook
+- Universal Household Authorization Form
+- Universal Shared Data Information System
+- Eligibility Income Verification Statement
+- Third Party Support
+
+## Traceability
+
+| TC | Automated Test Summary | Tags / Status |
+|----|------------------------|---------------|
+| TC-01 | Header, footer, and Resources title visible | `@auth` |
+| TC-02 | Resource document links visible | `@auth` |
+| TC-03 | Resource links open in new tabs and return successful document responses | `@auth`, currently marked `test.only` in spec |
+
+## Notes
+
+- The spec currently uses authenticated setup behavior through the `@auth` tag and waits for the **Logout** button before opening Resources.
+- `ApplicantPage.ts` contains the Resources page locators used by this suite.
+- The third test currently uses `test.only`; remove `.only` when the full test suite should run.
+- The current implementation expects all resource responses to contain `application/pdf`, even though two link labels end in `.docx`. If those resources are truly Word documents, update the assertion to accept the expected Word document content type.

package/specs/Applicant Self Register Page Test Plan.md

@@ -0,0 +1,190 @@
+# Polk County Applicant Self Register Page Test Plan
+
+## Application Overview
+
+Validate the Polk County Healthcare Plan Applicant **Self Registration** page at:
+
+`https://polkcounty--polkdevnew.sandbox.my.site.com/polkphpapplicant/s/polkselfregister?language=en_US`
+
+This flow lets new applicants create an account by providing identity, contact, and address information. This test plan covers URL and layout checks, required fields, address sections (physical and mailing), and consistency with other public applicant pages.
+
+---
+
+## Test Scenarios
+
+**File:** `ApplicantSelfRegisterPageTest.spec.ts`
+
+### Pre-condition (typical navigation)
+
+1. Open the applicant portal base URL with language parameter (e.g. `/polkphpapplicant/s/?language=en_US`).
+2. Click **Login** in the header to open the login panel.
+3. Click **Self Register** on the login page.
+4. Wait for the self-registration form to load (e.g. **Self Registration** heading is present).
+
+
+---
+
+#### 1. Verify redirect to the self register page and visibility of form sections
+**Steps:**
+1. Complete the pre-condition (or navigate directly to the self-register URL).
+2. Confirm the URL contains `polkphpapplicant/s/polkselfregister` (and optional `language=` query as applicable).
+3. Validate visibility of:
+   - **Self Registration** page title (heading)
+   - **Applicant First Name** label and textbox (required)
+   - **Applicant Middle Name** label and textbox (optional)
+   - **Applicant Last Name** label and textbox (required)
+   - **Suffix** label, combobox, and listbox when opened
+   - **Date of Birth** label, textbox, and date picker UI when the field is activated
+   - **Email Address** label and textbox (required)
+   - **Physical Address** card: section title, address lookup/combobox input, **Country**, **Street**, **City**, **State**, **ZIP** (labels and inputs; open **Country** and **State** dropdowns to confirm listboxes)
+   - **Mailing Address** card: section title, **Same as Physical** control, address lookup/combobox input, **Country**, **Street**, **City**, **State**, **ZIP** (same pattern as physical; open **Country** and **State** dropdowns to confirm listboxes)
+
+**Expected results:**
+- URL matches the self-register route.
+- All listed UI components render and are visible (no blocking error overlay).
+- Required-field indicators (e.g. asterisks on labels) match product rules for First Name, Last Name, Email, and any other required fields.
+
+---
+
+#### 2. Verify agreement / informational copy is present
+**Steps:**
+1. On the self-register page, locate the agreement or informational text block (typically near the form actions).
+**Expected results:**
+- Applicable legal or informational copy is displayed as designed (exact wording per product/legal).
+
+---
+
+#### 3. Verify required-field validation on submit (empty form)
+**Steps:**
+1. Reach the self-register page with all fields empty (defaults unchanged).
+2. Attempt to submit or proceed using the primary action (e.g. **Register** / **Submit** — exact label per build).
+3. Error Message for First Name, Last Name, Email should be displayed
+4. Enter the First Name, Last Name, Email and submit the form
+5. Error Message for the Physical Address & Mailing address should be displayed
+**Expected results:**
+- User cannot complete registration without required data; browser and/or inline validation appears for missing required fields (messages per Salesforce/app configuration).
+
+---
+
+#### 4. Verify invalid email format
+**Steps:**
+1. Fill other required fields with valid sample data (or minimal valid set per environment policy).
+2. Enter an invalid email (e.g. `notanemail`) in **Email Address**.
+3. Submit or trigger field-level validation.
+**Expected results:**
+
+- Validation error for email format is shown; submission does not succeed with invalid email.
+
+---
+
+#### 5. Verify Date of Birth constraints (if applicable)
+**Steps:**
+1. Open the **Date of Birth** control and attempt to select a future date, or enter a value outside allowed range per business rules.
+**Expected results:**
+- Invalid DOB is rejected or corrected per product rules (e.g. no future DOB for applicant).
+
+---
+
+#### 6. Verify Physical Address should only be in State of Florida
+**Steps:**
+1. Enter distinct values in **Physical Address** fields (where supported) not matching to Florida
+**Expected results:**
+- Error Message should be displayed
+
+---
+
+#### 7a. Verify Mailing Address should only be in Mailing must be in Florida
+**Steps:**
+1. Enter distinct values in **Mailing** fields (where supported) not matching to Approved Zip Codes
+**Expected results:**
+- Error Message should be displayed
+
+---
+
+#### 7b. Verify Mailing Address should only be ZIP must be in the approved Polk list
+**Steps:**
+1. Enter distinct values in **Mailing** fields (where supported) not matching to Approved Zip Codes
+**Expected results:**
+- Error Message should be displayed
+
+---
+
+#### 8. Verify **Same as Physical** toggle on Mailing Address
+**Steps:**
+1. Enter distinct values in **Physical Address** fields (where supported).
+2. Enable **Same as Physical** (if implemented as a toggle/checkbox).
+3. Observe mailing address fields.
+**Expected results:**
+- When enabled, mailing address mirrors physical address per design; when disabled, mailing fields can be edited independently.
+
+---
+
+#### 9. Verify physical vs mailing address independence when **Same as Physical** is off
+**Steps:**
+1. Ensure **Same as Physical** is off.
+2. Enter different mailing address values from physical address.
+3. Submit or save per allowed flow.
+**Expected results:**
+- Distinct physical and mailing values are accepted when the product allows separate addresses.
+
+---
+
+#### 10. Successful self-registration (happy path) — environment-dependent
+**Steps:**
+1. Complete all required fields with valid test data approved for the target org (including address selections that resolve in the address lookup).
+2. Accept any required agreements.
+3. Submit the form.
+**Expected results:**
+- Success path completes (e.g. confirmation message, email verification prompt, or redirect to login) per environment configuration; no unexpected error for valid data.
+
+---
+
+#### 11. Registering with the Same Name & Email (Duplicate Registration)
+**Steps:**
+1. Complete all required fields with valid test data approved for the target org with the Already Existing Same Name & Email 
+2. Submit the form.
+**Expected results:**
+- Error Message should be displayed
+
+---
+
+#### 12. Registering with the Long Names
+**Steps:**
+1. Complete all required fields with valid test data approved for the target org with the Long Names
+2. Submit the form.
+**Expected results:**
+- Error Message should be displayed
+
+---
+
+#### 13. Verify navigation back to Login (or portal home)
+**Steps:**
+1. From the self-register page, use **Back**, **Cancel**, or header navigation (e.g. **Login** / logo) as provided.
+**Expected results:**
+- User can leave the flow without a broken state; login or home is reachable as designed.
+
+---
+
+#### 14. Verify global chrome (header and footer)
+**Steps:**
+1. On the self-register page, confirm header (e.g. logo, **Login**) and scroll to the footer.
+**Expected results:**
+- Layout is consistent with other public applicant pages; critical chrome and footer links are present and not broken on typical viewports.
+
+---
+
+#### 15. Validating the values present in Suffix Dropdown
+**Steps:**
+1. On the self-register page, confirm header (e.g. logo, **Login**) and scroll to the footer.
+**Expected results:**
+- Layout is consistent with other public applicant pages; critical chrome and footer links are present and not broken on typical viewports.
+
+---
+
+#### 16. Validating the values present in Mailing Address - State Dropdown
+**Steps:**
+1. On the self-register page, confirm header (e.g. logo, **Login**) and scroll to the footer.
+**Expected results:**
+- Layout is consistent with other public applicant pages; critical chrome and footer links are present and not broken on typical viewports.
+
+---

package/specs/README.md

@@ -0,0 +1,3 @@
+# Specs
+
+This is a directory for test plans.

package/test-data/createApplication/formData.json

@@ -0,0 +1,42 @@
+{
+  "firstName": "John",
+  "lastName": "Doe",
+  "dob": "01-01-1990",
+  "ssn": "123456789",
+  "email": "john.doe123@test.com",
+  "landline": "1234567890",
+  "cellPhone": "1234567890",
+  "dropdowns": {
+    "preferredLanguage":["English","Spanish"],
+    
+    "race":["White/Caucasian","Black/African American","American Indian and Alaska Native","Asian","Native Hawaiian/Pacific Islander","Multi-Racial"],
+    "isPrimaryPhoneLandlineOrCellPhone": ["Landline","Cell Phone"],
+    "ethnicity":["Hispanic or Latino","Non-Hispanic or Non-Latino"],
+    "gender": ["Male", "Female"],
+    "maritalStatus": ["Married","Divorced","Widowed","Single","Legal Separation"],
+    "citizenship": ["Yes","No"],
+    "veteran": ["Yes","No"],
+    "language": ["English","Spanish","Arabic","ASL","Chinese","French","German","Japanese","Portuguese","Russian","Vietnamese","Creole","Hindi"],
+    "insuranceCoverage": ["Medicaid Full","Medicaid Share of Cost","Medicare","Private Insurance","Marketplace","Underinsured","Not Insured"],
+
+    "HousingQuestion": ["I have a steady place to live","Temporary Housing/Shelter","I do not have a steady place to live"],
+    "EnvironmentQuestion": ["Yes, help finding work","Yes, help keeping work","No"],
+    "SubstanceAbuseQuestion": ["Yes","No"],
+    "MentalHealthQuestion": ["Yes","No"],
+    "DisabilityQuestion1": ["Yes","No"],
+    "DisabilityQuestion2": ["Yes","No"]
+  },
+
+  "notWorkingExplaination": "Currently between positions; seeking work.",
+  "explain30DaysExpense": "Used savings and household resources for expenses.",
+  "receiveSupportForNecessities": ["Yes","No"],
+  "engageInFinancialTransactions": ["Yes","No"],
+  "uploadedDocumentsReferences": ["Proof of Self Employment","Paycheck 1", "401K Withdrawal", "Annuity Payments", "Dividends", "Interest Income", "Pension", "Rental Property", "Social Security Retirement","SSDI","Unemployment Compensation"],
+  
+  "enrollmentAcknowledgementText1": "Polk Healthcare Plan Agreement & Reimbursement Acknowledgement",
+  "enrollmentAcknowledgementText2": "Before submitting your application, please review the following terms and conditions. By Checking the box below, you confirm that you have read and agree to the provisions outlined in the Polk Healthcare Plan Rights and Privacy section. You can access the Plan Rights and Privacy Information here:",
+  "enrollmentAcknowledgementText3": "By Checking the box, you acknowledge and agree to the following:",
+  "enrollmentAcknowledgementText4": "I have read and agree to the terms outlined in the Polk Healthcare Plan Rights and Privacy information.I have read and agree to the terms outlined in the Polk Healthcare Plan Rights and Privacy information.",
+
+  "thankYouMessage": "Thank you for taking the time to complete the Application. We’ve received your information, and a case manager will reach out to you to discuss next steps."
+}

package/test-data/createApplication/textMessages.json

@@ -0,0 +1,52 @@
+{
+    "preferredLanguageError": "Error: Preferred Language is required.",
+    "firstNameRequiredError": "Error: First Name is required.",
+    "lastNameRequiredError": "Error: Last Name is required.",
+    "dobRequiredError": "Error: Date Of Birth (Use format dd-mm-yyyy) is required.",
+    "ssnRequiredError": "SSN is required.",
+    "emailRequiredError": "Error: Email is required",
+    "cellPhoneRequiredError": "Cell Phone is required.",
+    "isPrimaryPhoneLandlineOrCellPhoneRequiredError": "Error: is primary phone Landline or Cell Phone? is required.",
+    "raceRequiredError": "Error: Race is required.",
+    "ethnicityRequiredError": "Error: Ethnicity is required.",
+    "genderRequiredError": "Error: Gender is required.",
+    "maritalStatusRequiredError": "Error: Marital Status is required.",
+    "citizenshipRequiredError": "Error: U.S. Citizen/Permanent Resident Card Holder is required.",
+    "veteranRequiredError": "Error: Veteran is required.",
+    "languageRequiredError": "Error: Language is required.",
+    "insuranceCoverageRequiredError": "Error: Insurance Coverage is required.",
+    
+    "haveYouReceivedIncomeInLast30DaysRequiredError": "Error: Have you received income in last 30 days? is required.",
+    "whatTypeOfMonthlyIncomeDoesApplicantHaveRequiredError": "Error:  What type of MONTHLY income does applicant have​? Please select all income sources that apply is required.",
+    "employerNameRequiredError": "Error: Employer Name is required.",
+    "firstEmployerGrossMonthlyIncomeRequiredError": "Error: Gross Monthly Amount is required.",
+    "monthlyPensionAmountRequiredError": "Error: Monthly Pension Amount is required.",
+    "monthlyRentalPropertyAmountRequiredError": "Error: Monthly Rental Property Amount is required.",
+    "monthlySSDIAmountRequiredError": "Error: Monthly SSDI Amount is required.",
+    "monthly401KWithdrawalAmountRequiredError": "Error: Monthly 401K Withdrawal Amount is required.",
+    "monthlySocialSecurityRetirementAmountRequiredError": "Error: Monthly Social Security Retirement Amount is required.",
+    "monthlyUnemploymentCompensationAmountRequiredError": "Error: Monthly Unemployment Compensation Amount is required.",
+    "monthlyInterestIncomeAmountRequiredError": "Error: Monthly Interest Income Amount is required.",
+    "monthlyAnnuityPaymentsAmountRequiredError": "Error: Monthly Annuity Payments Amount is required.",
+    "monthlyDividendsAmountRequiredError": "Error: Monthly Dividends Amount is required.",
+    "iCanProvideSelfEmploymentValidationByTheFollowingMethodsRequiredError": "Error: I can provide self employment validation by the following methods is required.",
+    "pleaseEnterYourNameToCertifySelfEmploymentRequiredError": "Error: Please Enter your Name to certify Self Employment is required.",
+    "pleaseEnterTheDateOfTheCertificationTodayDateRequiredError": "Error: Please Enter the date of the certification ( Today's Date) is required.",
+    "whatTypeOfWorkDoYouPerformRequiredError": "Error: What type of work do you perform? is required.",
+    "monthlySelfEmployedAmountRequiredError": "Error: Monthly Self Employed Amount is required.",
+    "pleaseExplainWhyApplicantIsNotWorkingRequiredError": "Error: Please explain why applicant is not working? is required.",
+    "pleaseExplainHowYouHaveManagedForThePast30DaysWithoutIncomeRequiredError": "Error: Please explain how you have managed for the past 30 days without income (a 30-days Financial Statement may be required) is required.",
+    "doYouCurrentlyReceiveSupportFromAnyThirdPartiesForBasicNecessitiesSuchAsShelterFoodTransportationOrMedicalCareRequiredError": "Error: Do you currently receive support from any third parties for basic necessities such as shelter, food, transportation, or medical care? is required.",
+    "doYouEngageInAnyFinancialTransactionsWithInstitutionsOrPlatformsSuchAsBanksVenmoCashAppOrSimilarServicesRequiredError": "Error: Do you engage in any financial transactions with institutions or platforms such as banks, venmo, cash app, or similar services? is required.",
+    "pleaseSelectAtLeastOneOptionRequiredError": "Please select at least one option."
+
+
+
+
+
+
+
+
+
+
+}

package/test-data/forgotPassword/email.json

@@ -0,0 +1,5 @@
+{
+  "validEmail": "testuser@gmail.com",
+  "invalidEmail": "testuser",
+  "whitespaceEmail": "   "
+}

package/test-data/forgotPassword/textMessages.json

@@ -0,0 +1,5 @@
+{
+    "forgotPasswordMessage": "Enter your email (or username). If an account exists, we’ll send a reset link.",
+    "successMessage": "If an account exists for this email/username, a reset link has been sent.",
+    "invalidEmailError": "Email / UsernameEnter a valid email address, such as name@email.com."
+}

package/test-data/help/textContent.json

@@ -0,0 +1,48 @@
+{
+    "documentTitle": "Knowledge Base",
+    "htmlLang": "en-US",
+    "logoAlt": "Logo",
+    "h1Title": "Knowledge Base",
+    "subtitle": "Find answers to your questions",
+    "searchPlaceholder": "Search articles...",
+    "emptyStateMessage": "No articles found. Try a different search or category.",
+    "categoryLabels": ["All", "Support", "Account", "General"],
+    "articleTypeLabels": ["All", "FAQ", "Procedure"],
+    "articleCardBadge": "Procedure",
+    "articleCardTitle": "How to Reset Your Password",
+    "articleCardSummary": "Step-by-step guide to reset your account password quickly and securely",
+    "articleCardPublishDate": "4/16/2026, 5:03 AM",
+    "articleCardReadMore": "Read more →",
+    "articleDetailH1": "How to Reset Your Password",
+    "articleDetailBadge": "Procedure",
+    "articleDetailPublished": "Published: 4/16/2026, 5:03 AM",
+    "articleDetailCategory": "Category: Account",
+    "articleDetailArticleNumber": "Article #: 000001013",
+    "articleDetailSectionSummary": "Summary",
+    "articleDetailSectionAudience": "Audience",
+    "articleDetailSectionPurpose": "Purpose",
+    "articleDetailSectionSteps": "Steps",
+    "articleDetailSummaryText": "Step-by-step guide to reset your account password quickly and securely",
+    "articleDetailAudienceText": "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.",
+    "articleDetailPurposeText": "The purpose of this procedure is to guide users through the password reset process to regain access to their account safely without contacting support.",
+    "articleDetailWarningBullets": [
+        "⚠️ Warning: Do not share your password reset link with anyone.",
+        "⚠️ The reset link expires within 24 hours of being sent.",
+        "⚠️ After 5 failed attempts your account will be locked."
+    ],
+    "articleDetailSteps": [
+        "Step 1: Go to the login page and click \"Forgot Password\"",
+        "Step 2: Enter your registered email address and click Submit",
+        "Step 3: Check your email inbox for the password reset link",
+        "Step 4: Click the reset link within 24 hours",
+        "Step 5: Enter your new password (minimum 8 characters, must include 1 uppercase, 1 number, 1 special character)",
+        "Step 6: Confirm your new password and click Save",
+        "Step 7: Login with your new password successfully"
+    ],
+    "articleDetailHelpfulLabel": "Was this article helpful?",
+    "articleDetailYesButton": "👍 Yes",
+    "articleDetailNoButton": "👎 No",
+    "articleDetailBackButton": "← Back to Knowledge Base",
+    "articleUrlSlug": "how-to-reset-password",
+    "articleBannerAlt": "Polk County Banner"
+}