# Create UAT Test Cases – LandBank CRM

Generate a UAT-ready test case document for the LandBank CRM Individual Loan Application journey by navigating the live application using the Playwright MCP browser, observing the real UI, and writing test cases based only on what is actually present in the system.

## Dynamic Form Rule
If a field selection changes the modal or reveals new fields:
- immediately take a new `browser_snapshot`
- do not rely on earlier assumptions
- continue only with fields currently visible in the live UI
- if **Request OTP** is clicked and an **OTP** field appears, pause and ask the user for the OTP before continuing

## Arguments

`$ARGUMENTS` — optional. Pass a module name to generate test cases for a specific step only. Valid values:
- `lead` — TC only for Create Lead
- `prescreening` — TC only for Pre-Screening
- `opportunity` — TC only for Opportunity + Initiate Loan Application
- `consent` — TC only for Consent
- `verification` — TC only for Verification Outcomes
- `onboarding` — TC only for Pre-Onboarding Checklist
- *(leave blank)* — generate all 6 test cases end-to-end

---

## Output

Save the generated document to a **new file** each run. Check which version already exists and increment:
- If `UAT-INDIVIDUAL-APPLICATION-TEST-CASES-V4.md` exists → save as `V5.md`
- If `V5.md` exists → save as `V6.md`, and so on.

---

## Document Format

The document must open with a header block and Journey Overview table, followed by one section per test case.

### Document Header (top of file)

LandBank CRM – UAT Test Cases: Individual Loan Application Journey

Module: CRM – Individual Loan Application (End-to-End) Prepared by: Yohannes Libelo Date: [today's date] Version: v0[N] Target Environment: LandBank CRM Admin Portal Credentials: RM/CBA user account with access to Leads, Opportunities, and Inbox

---

Journey Overview

Step	Test Case	User	Applies To
1	TC-VN-001 – Create a Lead with OTP Consent	RM/CBA	Individual
2	TC-VN-002 – Pre-Screening Questionnaire and Lead Conversion	RM/CBA	Individual
3	TC-VN-003 – Capture Opportunity Details and Initiate Loan Application	RM/CBA	Individual
4	TC-VN-004 – Collect Applicant Consent (Electronic OTP or Manual Upload)	Applicant / RM/CBA	Individual
5	TC-VN-005 – Review and Approve Verification Outcomes	RM/CBA	Individual
6	TC-VN-006 – Complete the Pre-Onboarding Checklist	RM/CBA	Individual

### Per Test Case Structure

TC-VN-XXX – [Name]

Test Case Information

Field	Value
Test Case ID	TC-VN-XXX
Created By	Yohannes Libelo
Category	[category]
Creation Date	[today's date]
Test Type	Functional Testing (UAT)
User Type	RM/CBA

Requirements Covered

[Numbered list of what this test verifies, including the precondition as the last item]

Test Purpose

[One paragraph describing what this test confirms end-to-end]

Test Steps

#	Test Steps	Expected Results	Actual Results
N	[action]	[what the system should do]	TBD

Pass / Fail Criteria

Criterion	Pass Condition
[what to check]	[what counts as a pass]

**Rules:**
- Do NOT copy from any existing file — observe the live app only
- Every field name, button label, tab name, and status value must come from a `browser_snapshot`
- "Actual Results" column always contains **TBD** — never left blank
- Use exact wording from the UI — do not paraphrase labels
- There is NO "What the System Shows" section — observations are incorporated directly into Requirements Covered, Test Steps, and Pass / Fail Criteria
- Test steps column headers are: **# | Test Steps | Expected Results | Actual Results** (not "Test Step / Expected Result / Actual Result")

---

## Human Intervention Points

Only two points in the entire flow require human input — pause and wait at each:

1. **OTP (Step 1):** After clicking **Request OTP**, stop and ask the user for the OTP code received by email. Do not continue until it is provided.
2. **Consent (Step 4):** If testing Method A (email OTP consent), the applicant must click the consent link and enter the OTP themselves. For UAT purposes, use **Method B (manual upload)** via the Inbox to avoid this dependency and keep the flow automated.

All other steps must be completed by the agent without pausing.

---

## Known UI Behaviours (Do Not Skip)

These were discovered during live end-to-end testing and must be followed to avoid errors:

### Opportunity Form (Step 3)
- **Always click Edit before filling any fields** — the Opportunity detail page is read-only by default.
- **All three tabs (Client Info, Loan Info, Farms) must be filled** before clicking **+ Initiate Loan Application**. Clicking it with any tab incomplete shows the error: `"Cannot initiate workflow Please Fill in all required fields on the Client Info and Loan Info Tabs"`.
- **Fill all Client Info fields, not just the required ones** — some fields are not auto-populated from the lead (e.g. Country Of Residence, Citizenship, Client Title, Province). Fill every visible field on the Client Info tab even if it appears optional, before moving to Loan Info or Farms.
- **Marital Status is required** on the Client Info tab — do not leave it blank and always select Single
- **Products field uses an entity picker** — click the field to open the picker dialog, then **double-click** the desired row to select it.
- **Sources Of Income is a dropdown** — after making a selection, **press Escape to close the dropdown** before clicking the + Add button in the Loan Purpose table. Failing to close it causes a timeout error as the dropdown overlay blocks pointer events.
- **Loan Purpose sub-dialog** ("Add Loan Purpose(s)") requires: Purpose (dropdown), Purpose Description (text), Amount (number). Save the dialog before proceeding.
- **Farm sub-dialog** ("Create a Farm") req