- Backend: FastAPI app with all models, services, schemas, routes - Admin Panel: Next.js dashboard with all modules (CRM, POS, repairs, warranties, billing, notifications, etc.) - Ecommerce: storefront (submodule) + product catalog - AI Agents: .agents/ skill library for Antigravity IDE - Docs: architecture, billing, notification gateway markdown - Submodules: Backend/OpenWA, Ecommerce/File 2/storefront
98 lines
2.4 KiB
Markdown
98 lines
2.4 KiB
Markdown
---
|
|
description: Automated browser testing for ReloPortal features using chrome-devtools MCP
|
|
---
|
|
|
|
# Feature Testing Workflow
|
|
|
|
Use this workflow when the user asks you to test a feature or verify changes work correctly.
|
|
|
|
## When to Use
|
|
|
|
- User requests testing of a specific feature
|
|
- User provides a URL to test
|
|
- User wants to verify that code changes work end-to-end
|
|
- User wants to test multiple flows (create, edit, resubmit, upsert, etc.)
|
|
|
|
## Testing Process
|
|
|
|
### 1. Navigate to the provided URL
|
|
|
|
```bash
|
|
# Use chrome-devtools MCP
|
|
mcp1_new_page(url="PROVIDED_URL")
|
|
```
|
|
|
|
### 2. Login if needed
|
|
|
|
```bash
|
|
mcp1_fill(uid="username-uid", value="")
|
|
mcp1_fill(uid="password-uid", value="")
|
|
mcp1_click(uid="login-button-uid")
|
|
```
|
|
|
|
### 3. Take snapshot to understand page structure
|
|
|
|
```bash
|
|
mcp1_take_snapshot()
|
|
```
|
|
|
|
### 4. Execute the specific test scenario
|
|
|
|
- Create orders/records
|
|
- Submit forms
|
|
- Test resubmit flows
|
|
- Test upsert operations
|
|
- Verify data persistence
|
|
|
|
### 5. Check for errors
|
|
|
|
```bash
|
|
mcp1_list_console_messages()
|
|
```
|
|
|
|
### 6. Report results
|
|
|
|
- What worked
|
|
- What failed
|
|
- Network request payloads (verify childServiceRequestId handling)
|
|
- Any errors in console
|
|
|
|
## Testing Checklist for Home Sale Services
|
|
|
|
For each Home Sale sub-service (BMA, Title, VDI, Equity, Appraisal, Inspection, Listing Contract sections, Inventory sections):
|
|
|
|
1. **Create flow (initiate)**
|
|
|
|
- Navigate to service tab
|
|
- Create a simple order/record with 1 detail
|
|
- Save
|
|
- Verify: payload should NOT contain childServiceRequestId
|
|
|
|
2. **Resubmit flow (update)**
|
|
|
|
- Edit existing order
|
|
- Add new detail or modify existing
|
|
- Resubmit
|
|
- Verify: payload should NOT contain childServiceRequestId
|
|
|
|
3. **Upsert flow**
|
|
- Edit existing order
|
|
- Modify detail
|
|
- Save (uses upsert when useUpsertOnUpdate is true)
|
|
- Verify: payload should contain both id and childServiceRequestId in detail rows, parentServiceRequestId at top level
|
|
|
|
## Network Request Verification
|
|
|
|
When testing Home Sale upsert changes, specifically check:
|
|
|
|
- `transfereeProfileService.upsertHomeSaleDetails` calls
|
|
- Verify `parentServiceRequestId` is at top level
|
|
- Verify `childServiceRequestId` is in detail rows
|
|
- Verify `id` is separate from `childServiceRequestId` in detail rows
|
|
|
|
## Notes
|
|
|
|
- Always take snapshots before and after actions to verify state changes
|
|
- Check console for errors after each action
|
|
- Use `mcp1_list_network_requests()` to inspect API payloads
|
|
- If login page appears, use saved credentials ()
|