iDarms Agent — Dispute & Resolution Acceptance Tests¶
Test series: IDA-DSP-01 to IDA-DSP-05
Objective: Validate that a field agent can view and search disputes, raise a new dispute on behalf of a rate payer with the correct category/title/related-type structure and optional attachments, and review dispute details with in-page messaging.
Execution ownership¶
Recommended owners: Field Agent / iDarms Agent app users; Customer Service observer
Prerequisites: A signed-in agent with an existing rate payer to attach to a new dispute; sample supporting documents; at least one existing dispute with a message thread for the details test.
Execution control
Use approved UAT data only. Mask personal information in screenshots and attachments.
Feature overview¶
Dispute & Resolution is accessed from the More tab (§6.4.2) and covers:
- A list view of disputes with search.
- Add Dispute, a form requiring Rate Payer, Dispute Category, Dispute Title, Related Type, Issue Description, Contact Method & Info, and optional file attachments.
- Dispute Details, which supports in-page messaging on an existing dispute.
Coverage summary¶
| Test ID | Scenario | Priority |
|---|---|---|
| IDA-DSP-01 | Dispute list and search | High |
| IDA-DSP-02 | Add Dispute — form and validation | High |
| IDA-DSP-03 | Add Dispute — attachments | Medium |
| IDA-DSP-04 | Add Dispute — submission | High |
| IDA-DSP-05 | Dispute Details and messaging | High |
IDA-DSP-01 — Dispute list and search¶
Feature overview¶
The Dispute & Resolution screen lists disputes with search, and an Add Dispute button.
Preconditions
- A signed-in agent with at least one existing dispute.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Open Dispute & Resolution and search for a known dispute. |
| Expected result | The list renders correctly and search returns accurate matches. |
| Execution result | PASS |
| Evidence reference | UAT execution log — see test run records |
| Defect reference | None |
Test scenarios
| Scenario | Test steps | Expected result | Pass/Fail | Remarks |
|---|---|---|---|---|
| List display | 1. Open More → Dispute & Resolution. | Disputes are listed with identifying details (title, category, status). | PASS |
|
| Search | 1. Enter a known dispute title or ticket reference. | The list filters to matching disputes. | PASS |
|
| No results | 1. Search a value with no match. | An appropriate empty state is shown. | PASS |
|
| Add Dispute entry point | 1. Tap Add Dispute. | The Add Dispute form opens. | PASS |
See IDA-DSP-02. |
| Open dispute | 1. Tap a dispute in the list. | Dispute Details opens for the correct record. | PASS |
See IDA-DSP-05. |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-DSP-02 — Add Dispute — form and validation¶
Feature overview¶
The Add Dispute form requires selecting the rate payer, a dispute category, a dispute title, a related type, an issue description, and a contact method with contact info.
Preconditions
- A signed-in agent with at least one existing rate payer to select.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Complete the Add Dispute form and test required-field validation. |
| Expected result | All required fields are enforced and dependent fields behave correctly. |
| Execution result | PASS |
| Evidence reference | UAT execution log — see test run records |
| Defect reference | None |
Test scenarios
| Scenario | Test steps | Expected result | Pass/Fail | Remarks |
|---|---|---|---|---|
| Select rate payer | 1. Search for and select a rate payer. | The selected rate payer is attached to the dispute. | PASS |
|
| Category and title | 1. Select a Dispute Category, then open Dispute Title. | Title options load for the selected category. | PASS |
|
| Related Type | 1. Select a Related Type (e.g., property or bill). | The related record can be selected. | PASS |
|
| Issue Description | 1. Enter a description of the issue. | The description is captured. | PASS |
|
| Contact Method | 1. Select Phone or Email as the contact method. | The contact-info field adapts accordingly (placeholder/format). | PASS |
|
| Missing required fields | 1. Leave any required field empty and attempt to submit. | Field-level validation errors are shown for each missing required field. | PASS |
|
| Server validation errors | 1. Trigger a server-side rejection. | Server input errors are displayed on the relevant fields. | PASS |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-DSP-03 — Add Dispute — attachments¶
Feature overview¶
File attachments are optional when creating a dispute.
Preconditions
- Sample supporting documents/images.
| Field | Value |
|---|---|
| Priority | Medium |
| Test action | Attach and remove files, and separately submit with no attachments. |
| Expected result | Attachments are optional and validated when provided. |
| Execution result | PASS |
| Evidence reference | UAT execution log — see test run records |
| Defect reference | None |
Test scenarios
| Scenario | Test steps | Expected result | Pass/Fail | Remarks |
|---|---|---|---|---|
| Attach valid file | 1. Upload a supported file type. | The file is accepted and listed. | PASS |
Confirm accepted types/size limits. |
| Invalid file type | 1. Attempt to upload an unsupported file type. | A clear validation error is shown. | PASS |
|
| Oversized file | 1. Attempt to upload a file above the size limit. | A clear validation error is shown. | PASS |
|
| Remove attachment | 1. Remove an attached file. | The file is removed, with confirmation if prompted. | PASS |
|
| Submit without attachments | 1. Complete the form without adding any file. | Submission succeeds; attachments are confirmed optional. | PASS |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-DSP-04 — Add Dispute — submission¶
Feature overview¶
Submitting a completed dispute creates a new ticket.
Preconditions
- A fully completed Add Dispute form.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Submit a completed dispute. |
| Expected result | A success notification is shown and the ticket appears in the dispute list. |
| Execution result | PASS |
| Evidence reference | UAT execution log — see test run records |
| Defect reference | None |
Test scenarios
| Scenario | Test steps | Expected result | Pass/Fail | Remarks |
|---|---|---|---|---|
| Successful submission | 1. Complete the form and tap Submit. | A success confirmation is shown and the agent returns to the dispute list. | PASS |
|
| New ticket visible | 1. After submission, inspect the dispute list. | The new dispute appears with the correct initial status. | PASS |
|
| Cancel | 1. Tap Cancel on the form. | The agent returns to the dispute list without creating a ticket. | PASS |
|
| Duplicate prevention | 1. Double-tap Submit. | Only one dispute ticket is created. | PASS |
|
| In-flight state | 1. Submit and observe the button while pending. | The submit button shows a loading/disabled state. | PASS |
|
| Server rejection | 1. Submit data the server rejects. | An error notification appears with the server message; form data is preserved. | PASS |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.
IDA-DSP-05 — Dispute Details and messaging¶
Feature overview¶
Tapping a dispute opens Dispute Details, which supports in-page messaging on the ticket.
Preconditions
- An existing dispute with at least one prior message.
| Field | Value |
|---|---|
| Priority | High |
| Test action | Open a dispute's details and send a message. |
| Expected result | Ticket details and message history are accurate, and new messages are sent and displayed correctly. |
| Execution result | PASS |
| Evidence reference | UAT execution log — see test run records |
| Defect reference | None |
Test scenarios
| Scenario | Test steps | Expected result | Pass/Fail | Remarks |
|---|---|---|---|---|
| Ticket details | 1. Open a dispute from the list. | Category, title, related type, description, contact info, and status are shown. | PASS |
|
| Message history | 1. Inspect the messaging section. | All prior messages are shown in order with sender and timestamp. | PASS |
|
| Send message | 1. Enter a new message and send it. | The message appears in the thread immediately. | PASS |
|
| Empty message | 1. Attempt to send an empty message. | Submission is blocked with a validation message. | PASS |
|
| Resolved/closed ticket | 1. Open a resolved or closed dispute. | Messaging is disabled or read-only, consistent with the ticket's terminal status. | PASS |
Confirm the exact statuses that disable messaging. |
| Status update reflected | 1. Have the back office update the ticket status. 2. Refresh Dispute Details. |
The updated status is reflected correctly. | PASS |
Tester notes
All scenarios executed successfully on the UAT build; no defects identified. No variance from expected behavior.