@trevordsouzabrite/test-package 1.0.0

package/specs/Applicant My Medical Coverage Page Test Plan.md

@@ -0,0 +1,689 @@
+# Polk County Applicant My Medical Coverage Page Test Plan
+
+## Application Overview
+
+Validate the Polk County Healthcare Plan Applicant **My Medical Coverage** page at `/polkphpapplicant/s/enrollments?language=en_US`.
+
+The page is an authenticated applicant portal page. Current exploration found browser title **Enrollments**, authenticated header/footer navigation, an enrollment summary table, action controls for **Change Provider** and **Enrollment card**, a **Update My Information** action, a **Billing Inquiries** action, and a **My Request Status** section. The explored account showed one active PHP enrollment with beneficiary, program, status, coverage begin date, coverage end date, and provider information.
+
+Tests tagged `@auth` require a valid authenticated applicant session. Tests tagged `@no-auth` must run without stored authentication state.
+
+## Shared Preconditions
+
+| Step | Action | Expected Result |
+|------|--------|-----------------|
+| 1 | Authenticate with a valid applicant account or reuse `playwright/.auth/user.json` | Applicant session is active |
+| 2 | Navigate to `/polkphpapplicant/s/?language=en_US` | Applicant dashboard loads with **Logout** visible |
+| 3 | Click **My Medical Coverage** in the authenticated header | User lands on `/polkphpapplicant/s/enrollments?language=en_US` |
+| 4 | Wait for page title **Enrollments** and enrollment page content | Page is ready for assertions |
+
+## Test Scenarios
+
+### TC-01 - Authenticated My Medical Coverage Page Loads
+
+**Automated file:** `tests/ApplicantMyMedicalCoveragePageTest.spec.ts`
+
+**Tags:** `@auth @smoke`
+
+**Steps:**
+
+1. Start from an authenticated applicant session.
+2. Navigate to the applicant dashboard.
+3. Click **My Medical Coverage**.
+4. Verify the URL contains `/enrollments`.
+5. Verify browser title is **Enrollments**.
+
+**Expected Result:** The authenticated applicant can open the My Medical Coverage page without being redirected to login or an error page.
+
+---
+
+### TC-02 - Authenticated Header And Footer Are Visible
+
+**Automated test:** `Verify the header & footer sections are visible on the my medical coverage page @auth`
+
+**Tags:** `@auth`
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Verify header elements: logo, **Home**, **Create Application**, **My Applications**, **My Medical Coverage**, **Resources**, **Help**, **Privacy Policy**, and **Logout**.
+3. Scroll to the footer.
+4. Verify footer image, address, phone number, business hours, footer links, and copyright.
+
+**Expected Result:** Shared authenticated portal chrome is present and consistent with other applicant pages.
+
+---
+
+### TC-03 - Enrollment Summary Table Displays For Applicant With Coverage
+
+**Tags:** `@auth @smoke`
+
+**Precondition:** Applicant has at least one enrollment record.
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Verify the enrollment summary area is visible.
+3. Verify columns are shown: **Beneficiary**, **Program**, **Status**, **Coverage Begin Date**, **Coverage End Date**, and **Actions**.
+4. Verify each visible enrollment row has beneficiary name, program, status, begin date, and end date values.
+
+**Expected Result:** Active or historical enrollment records render in a readable table without missing required columns.
+
+---
+
+### TC-04 - Enrollment Row Date And Status Formatting
+
+**Tags:** `@auth`
+
+**Steps:**
+
+1. Open My Medical Coverage for an applicant with coverage.
+2. Read the **Status** value.
+3. Read **Coverage Begin Date** and **Coverage End Date**.
+4. Verify the date values use a user-readable format such as `Mar 30, 2026`.
+
+**Expected Result:** Coverage status and date fields are populated and formatted consistently.
+
+---
+
+### TC-05 - No Enrollment Empty State
+
+**Tags:** `@auth`
+
+**Precondition:** Use or seed an applicant account with no enrollment records.
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Wait for enrollment content to finish loading.
+3. Verify the page shows **DID NOT FIND ANY ENROLLMENT RECORDS.**
+4. Verify header, footer, and main navigation remain available.
+
+**Expected Result:** Applicants with no enrollments receive a clear empty state and are not shown a blank page.
+
+---
+
+### TC-06 - Change Provider Modal Opens
+
+**Tags:** `@auth @smoke`
+
+**Precondition:** Applicant has an enrollment with the **Change Provider** action.
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Click **Change Provider**.
+3. Verify the modal opens with title **Change Provider**.
+4. Verify instruction text: **Select a new primary care provider below.**
+5. Verify required fields are visible:
+   - **Search and select your new primary care provider**
+   - **Tell us why you’re changing your Primary Care Provider (PCP)**
+6. Verify **Close** and **Submit** controls are visible.
+
+**Expected Result:** Change Provider opens in a modal without leaving the Enrollments page.
+
+---
+
+### TC-07 - Change Provider Empty Submit Validation
+
+**Tags:** `@auth @validation`
+
+**Steps:**
+
+1. Open the **Change Provider** modal.
+2. Leave provider search blank.
+3. Leave reason dropdown unselected.
+4. Click **Submit**.
+
+**Expected Result:**
+
+- Provider field shows **Complete this field.**
+- Reason field shows **Complete this field.**
+- Error notification is displayed.
+- The modal remains open and no provider change request is submitted.
+
+---
+
+### TC-08 - Change Provider Close Does Not Submit
+
+**Tags:** `@auth`
+
+**Steps:**
+
+1. Open the **Change Provider** modal.
+2. Click **Close** without entering data.
+3. Reopen My Medical Coverage or inspect the enrollment row.
+
+**Expected Result:** Modal closes, the user remains on My Medical Coverage, and provider/status data is unchanged.
+
+---
+
+### TC-09 - Change Provider Provider Search Behavior
+
+**Tags:** `@auth`
+
+**Steps:**
+
+1. Open the **Change Provider** modal.
+2. Type a valid provider name or partial provider name into the provider search field.
+3. Wait for search results.
+4. Select a provider.
+
+**Expected Result:** Matching providers are displayed, a provider can be selected, and the selected provider remains visible in the field.
+
+---
+
+### TC-10 - Change Provider No-Match Search
+
+**Tags:** `@auth @edge`
+
+**Steps:**
+
+1. Open the **Change Provider** modal.
+2. Search for a provider name that should not exist.
+3. Wait for lookup results.
+
+**Expected Result:** The lookup shows a clear no-results state and does not select an unintended provider.
+
+---
+
+### TC-11 - Change Provider Submit With Missing Reason
+
+**Tags:** `@auth @validation`
+
+**Steps:**
+
+1. Open the **Change Provider** modal.
+2. Select a valid provider.
+3. Leave **Choose Reason** unselected.
+4. Click **Submit**.
+
+**Expected Result:** Reason field validation blocks submission and the selected provider remains populated.
+
+---
+
+### TC-12 - Change Provider Submit With Missing Provider
+
+**Tags:** `@auth @validation`
+
+**Steps:**
+
+1. Open the **Change Provider** modal.
+2. Select a reason.
+3. Leave provider search blank.
+4. Click **Submit**.
+
+**Expected Result:** Provider field validation blocks submission and the selected reason remains populated.
+
+---
+
+### TC-13 - Change Provider Successful Submission
+
+**Tags:** `@auth`
+
+**Precondition:** Use test data where submitting a provider change request is safe and expected.
+
+**Steps:**
+
+1. Open the **Change Provider** modal.
+2. Select a valid new provider.
+3. Select a valid reason.
+4. Click **Submit**.
+5. Wait for success or request-status update.
+
+**Expected Result:** Provider change request is submitted once, a success confirmation appears, and **My Request Status** reflects the submitted request.
+
+---
+
+### TC-14 - My Request Status Displays Current Provider Change Request
+
+**Tags:** `@auth`
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Inspect the **My Request Status** section.
+3. Verify columns or labels such as **Status**, **Effective Date**, and **Reference**.
+4. Verify the current provider reference is displayed when present.
+
+**Expected Result:** Request status content is visible and readable. Current exploration showed **Effective**, an effective date, and provider-on-file reference text.
+
+---
+
+### TC-15 - Enrollment Card Generates PDF
+
+**Tags:** `@auth @smoke`
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Click **Enrollment card** for an enrollment row.
+3. Wait for navigation or download.
+4. Verify the browser navigates to `/polkphpapplicant/s/enrollmentcard`.
+5. Verify a PDF download is initiated.
+
+**Expected Result:** The enrollment card route loads and downloads **EnrollmentCard.pdf** from the Visualforce PDF endpoint.
+
+---
+
+### TC-16 - Enrollment Card Uses Selected Enrollment Record
+
+**Tags:** `@auth`
+
+**Precondition:** Applicant has more than one enrollment record.
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Click **Enrollment card** on the first enrollment row.
+3. Capture the `recordId` in the enrollment-card URL or generated PDF request.
+4. Return to My Medical Coverage.
+5. Click **Enrollment card** on a different enrollment row.
+
+**Expected Result:** Each card request uses the selected row's enrollment record ID and does not generate another member's card.
+
+---
+
+### TC-17 - Update My Information Action
+
+**Tags:** `@auth`
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Click **Update My Information**.
+3. Wait for navigation, modal, or toast.
+
+**Expected Result:** The user is either routed to the correct update-information application flow or shown a clear error. Current exploration for the available test account displayed toast text **Error No application found.**
+
+---
+
+### TC-18 - Update My Information Error Is Dismissible
+
+**Tags:** `@auth @validation`
+
+**Steps:**
+
+1. Click **Update My Information** for an account without a matching application.
+2. Verify the **Error No application found.** toast appears.
+3. Click the toast **Close** control.
+
+**Expected Result:** Toast closes, the user remains on My Medical Coverage, and no broken page state remains.
+
+---
+
+### TC-19 - Billing Inquiries Page Opens
+
+**Tags:** `@auth @smoke`
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Click **Billing Inquiries**.
+3. Wait for navigation.
+4. Verify URL contains `/billing-inquiries`.
+5. Verify browser title is **Billing_Inquiries**.
+6. Verify heading text **Billing Inquiry** and explanatory instructions are visible.
+
+**Expected Result:** Billing Inquiry form opens from My Medical Coverage and retains authenticated header/footer.
+
+---
+
+### TC-20 - Billing Inquiry Form Required Fields Are Visible
+
+**Tags:** `@auth`
+
+**Steps:**
+
+1. Open Billing Inquiries from My Medical Coverage.
+2. Verify required fields:
+   - **Tell us why you believe these services should be covered under your PolkHealthCare Plan benefits**
+   - **Date of Service**
+   - **Amount Due**
+   - **Select Application Member**
+   - **Appeal Reason**
+   - **Provider or Facility Name**
+   - **Type of document uploaded**
+3. Verify optional/conditional fields:
+   - **Was any portion of this bill already paid by another provider or insurance company?**
+   - **Claim #**
+   - **Amount paid by other provider**
+4. Verify file upload area is visible.
+
+**Expected Result:** All fields required to submit a billing inquiry are visible and labeled.
+
+---
+
+### TC-21 - Billing Inquiry Empty Submit Requires Upload
+
+**Tags:** `@auth @validation`
+
+**Steps:**
+
+1. Open Billing Inquiries.
+2. Do not upload a file.
+3. Click **Submit**.
+
+**Expected Result:** Error toast displays **Please upload at least one document.** and submission is blocked.
+
+---
+
+### TC-22 - Billing Inquiry Missing Required Field Validation
+
+**Tags:** `@auth @validation`
+
+**Steps:**
+
+1. Open Billing Inquiries.
+2. Upload a valid test document.
+3. Leave required text, date, amount, member, appeal reason, provider/facility, and document type fields blank.
+4. Click **Submit**.
+
+**Expected Result:** Each missing required field shows inline validation and no request is submitted.
+
+---
+
+### TC-23 - Billing Inquiry File Upload Accepts Supported Documents
+
+**Tags:** `@auth`
+
+**Steps:**
+
+1. Open Billing Inquiries.
+2. Upload a supported file type such as PDF or image.
+3. Verify the uploaded file appears in the upload list.
+4. Remove the file.
+
+**Expected Result:** Supported files can be uploaded and removed before submission.
+
+---
+
+### TC-24 - Billing Inquiry Rejects Unsupported Or Oversized Files
+
+**Tags:** `@auth @edge`
+
+**Steps:**
+
+1. Open Billing Inquiries.
+2. Attempt to upload an unsupported file type.
+3. Attempt to upload a file larger than the configured limit.
+
+**Expected Result:** The form blocks unsupported or oversized uploads with a clear error and does not submit partial data.
+
+---
+
+### TC-25 - Billing Inquiry Amount Validation
+
+**Tags:** `@auth @validation`
+
+**Steps:**
+
+1. Open Billing Inquiries.
+2. Enter invalid values into **Amount Due**, such as letters, negative values, zero where not allowed, and more than two decimal places.
+3. Move focus away from the field or submit.
+
+**Expected Result:** Invalid amount values are rejected with clear field-level validation.
+
+---
+
+### TC-26 - Billing Inquiry Date Validation
+
+**Tags:** `@auth @validation`
+
+**Steps:**
+
+1. Open Billing Inquiries.
+2. Enter invalid date formats into **Date of Service**.
+3. Enter a future date.
+4. Submit the form.
+
+**Expected Result:** Invalid or future service dates are rejected according to business rules.
+
+---
+
+### TC-27 - Billing Inquiry Cancel Returns Safely
+
+**Tags:** `@auth`
+
+**Steps:**
+
+1. Open Billing Inquiries.
+2. Enter partial form data.
+3. Click **Cancel**.
+4. Confirm any unsaved-change prompt if shown.
+
+**Expected Result:** User returns safely without submitting a billing inquiry or leaving partial data in a submitted state.
+
+---
+
+### TC-28 - Billing Inquiry Successful Submission
+
+**Tags:** `@auth`
+
+**Precondition:** Use controlled test data where creating a billing inquiry is allowed.
+
+**Steps:**
+
+1. Open Billing Inquiries.
+2. Complete all required fields with valid data.
+3. Upload the full bill or claim document.
+4. Click **Submit**.
+5. Wait for confirmation.
+
+**Expected Result:** Billing inquiry is submitted once, success confirmation is shown, and request status or downstream case data reflects the new inquiry.
+
+---
+
+### TC-29 - Direct Unauthenticated Access Redirects To Login
+
+**Tags:** `@no-auth @smoke`
+
+**Steps:**
+
+1. Create a new browser context without storage state.
+2. Navigate directly to `/polkphpapplicant/s/enrollments?language=en_US`.
+3. Wait for navigation.
+
+**Expected Result:**
+
+- User is redirected to `/polkphpapplicant/s/login/`.
+- URL contains `ec=302`.
+- URL contains `startURL=%2Fpolkphpapplicant%2Fs%2Fenrollments`.
+- Login form shows **UserName**, **Password**, **Log In**, **Forgot password?**, and **Sign Up**.
+
+---
+
+### TC-30 - Login Redirect Returns To My Medical Coverage
+
+**Tags:** `@no-auth`
+
+**Steps:**
+
+1. Navigate directly to My Medical Coverage without auth.
+2. Complete login with valid credentials.
+3. Wait for post-login navigation.
+
+**Expected Result:** User lands on My Medical Coverage because the login URL preserved the requested `startURL`.
+
+---
+
+### TC-31 - Logout Protects My Medical Coverage
+
+**Tags:** `@auth`
+
+**Steps:**
+
+1. Open My Medical Coverage with an authenticated session.
+2. Click **Logout**.
+3. Attempt to navigate back to `/polkphpapplicant/s/enrollments?language=en_US`.
+
+**Expected Result:** User cannot view enrollment data after logout and is redirected to login.
+
+---
+
+### TC-32 - Unauthorized Enrollment Record Access
+
+**Tags:** `@auth @security`
+
+**Steps:**
+
+1. Authenticate as Applicant A.
+2. Attempt to open an enrollment-card URL or enrollment route with a record ID belonging to Applicant B or a nonexistent record.
+
+**Expected Result:** The page shows safe access-denied/not-found behavior or redirects. No other applicant's enrollment data or PDF is exposed.
+
+---
+
+### TC-33 - Multiple Enrollment Records
+
+**Tags:** `@auth @edge`
+
+**Precondition:** Applicant has multiple active or historical enrollments.
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Verify all enrollment rows are visible or paginated/scrollable.
+3. Verify each row has independent **Change Provider** and **Enrollment card** actions.
+4. Run the action tests against a non-first row.
+
+**Expected Result:** Row actions apply to the selected enrollment and do not always use the first record.
+
+---
+
+### TC-34 - Expired Or Inactive Coverage Display
+
+**Tags:** `@auth @edge`
+
+**Precondition:** Applicant has inactive, expired, terminated, or future-dated coverage.
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Verify inactive or expired enrollment rows display their status and dates.
+3. Inspect available row actions.
+
+**Expected Result:** Historical/future coverage is clear to the applicant. Actions that should not apply to inactive coverage are hidden or disabled.
+
+---
+
+### TC-35 - Keyboard Navigation
+
+**Tags:** `@auth @accessibility`
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Use `Tab` and `Shift+Tab` through header links, enrollment row actions, request status content, billing/update buttons, and footer links.
+3. Activate **Change Provider**, **Enrollment card**, and **Billing Inquiries** using keyboard controls.
+4. Dismiss modals or toasts with keyboard controls.
+
+**Expected Result:** Focus is visible, focus order is logical, and all interactive page features are reachable without a mouse.
+
+---
+
+### TC-36 - Accessible Names And Semantics
+
+**Tags:** `@auth @accessibility`
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Verify row action controls have clear accessible names.
+3. Verify the enrollment table or table-like region exposes column and row relationships to assistive technology.
+4. Open Change Provider and verify the modal has dialog semantics, focus management, labels, required-state communication, and an accessible close control.
+5. Open Billing Inquiries and verify all inputs, dropdowns, file upload controls, and toasts are accessible.
+
+**Expected Result:** Screen reader users can identify the page, enrollment data, actions, modal fields, validation errors, and toast messages.
+
+---
+
+### TC-37 - Axe Accessibility Baseline
+
+**Tags:** `@auth @accessibility`
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Run Axe with WCAG 2.x A/AA rules.
+3. Repeat after opening the Change Provider modal.
+4. Repeat on Billing Inquiries.
+
+**Expected Result:** No critical or serious accessibility violations are present in the main page, modal, or Billing Inquiries form.
+
+---
+
+### TC-38 - Responsive Layout
+
+**Tags:** `@auth`
+
+**Steps:**
+
+1. Open My Medical Coverage at desktop viewport.
+2. Repeat at tablet viewport.
+3. Repeat at mobile viewport.
+4. Verify the enrollment table, action controls, Change Provider modal, Billing Inquiries form, request status section, header, and footer remain usable.
+
+**Expected Result:** Text does not overlap, table data remains readable or scrollable, action controls stay reachable, and modal/form content fits the viewport.
+
+---
+
+### TC-39 - Browser Console And Network Health
+
+**Tags:** `@auth`
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Monitor console messages and failed network requests during initial load.
+3. Click Change Provider, Enrollment card, Update My Information, and Billing Inquiries.
+4. Monitor console messages and failed network requests after each action.
+
+**Expected Result:** No application-critical failed requests or uncaught product errors occur. Framework warnings should be reviewed but should not fail the test unless they affect user behavior.
+
+---
+
+### TC-40 - Data Privacy In Enrollment And PDF Output
+
+**Tags:** `@auth @security`
+
+**Steps:**
+
+1. Open My Medical Coverage.
+2. Verify only the authenticated applicant's enrollment information is shown.
+3. Generate the enrollment card PDF.
+4. Verify the PDF contains only the selected applicant/enrollment data.
+5. Confirm URLs and client-side data do not expose unrelated applicant IDs or sensitive data.
+
+**Expected Result:** Enrollment data and generated PDFs are scoped to the authenticated applicant.
+
+## Traceability
+
+| Area | Covered By |
+|------|------------|
+| Authenticated page load and chrome | TC-01, TC-02 |
+| Enrollment data and empty states | TC-03, TC-04, TC-05 |
+| Change Provider modal and validation | TC-06, TC-07, TC-08, TC-09, TC-10, TC-11, TC-12, TC-13 |
+| Request status | TC-14 |
+| Enrollment card PDF | TC-15, TC-16 |
+| Update information | TC-17, TC-18 |
+| Billing inquiries | TC-19, TC-20, TC-21, TC-22, TC-23, TC-24, TC-25, TC-26, TC-27, TC-28 |
+| Authentication and authorization | TC-29, TC-30, TC-31, TC-32 |
+| Edge cases | TC-33, TC-34 |
+| Accessibility and responsive behavior | TC-35, TC-36, TC-37, TC-38 |
+| Observability and privacy | TC-39, TC-40 |
+
+## Exploration Notes
+
+- `mcp__playwright_test__` planner setup returned `Transport closed`; local Playwright exploration was used to inspect the authenticated page.
+- Auth setup was refreshed with `tests/auth.setup.ts` before exploration.
+- Current explored authenticated route: `/polkphpapplicant/s/enrollments?language=en_US`.
+- Current explored page title: **Enrollments**.
+- Current explored active enrollment displayed program **PHP**, status **Active**, and coverage dates **Mar 30, 2026** to **Mar 29, 2027**.
+- Clicking **Change Provider** opened a modal with provider search, reason dropdown, **Close**, and **Submit**.
+- Empty **Change Provider** submission displayed **Complete this field.** for both required fields.
+- Clicking **Enrollment card** navigated to `/polkphpapplicant/s/enrollmentcard?...` and initiated **EnrollmentCard.pdf** download.
+- Clicking **Update My Information** for the explored account displayed toast **Error No application found.**
+- Clicking **Billing Inquiries** navigated to `/polkphpapplicant/s/billing-inquiries?language=en_US`.
+- Empty Billing Inquiry submission displayed toast **Please upload at least one document.**
+- Unauthenticated direct access to `/polkphpapplicant/s/enrollments?language=en_US` redirected to login with `ec=302` and a `startURL` back to the enrollments route.