Skip to content

iDARMS Frontend (Back Office) — Dispute Resolution Module Acceptance Tests

Test series: IDA-DSP-01 to IDA-DSP-08
Objective: Validate that dispute setup (categories, titles, dependencies), dispute tickets, and claim requests can be created, tracked, and resolved through the Back Office.

Execution ownership

Recommended owners: System Super-Admin; Dispute/Resolution business owner; Customer Service observer

Prerequisites: A signed-in administrator, seeded dispute setup data, and claim requests in the UAT environment.

Execution control

Use approved UAT data only. Mask personal, authentication, and payment information in screenshots and attachments.

Feature overview

The Dispute Resolution module covers:

  • Dispute Categories, Titles, and Dependencies setup.
  • Add Dispute — creation of a dispute claim request.
  • List Dispute, Resolution, and Claim Requests queues.
  • Claim Request Details — a helpdesk workspace with replies, attachments, and status changes.

Coverage summary

Test ID Feature Scenario Priority
IDA-DSP-01 Setup Dispute categories High
IDA-DSP-02 Setup Dispute titles High
IDA-DSP-03 Setup Dependencies High
IDA-DSP-04 Add Dispute Claim request creation Critical
IDA-DSP-05 List Dispute Ticket list and filters Critical
IDA-DSP-06 Resolution Resolved requests High
IDA-DSP-07 Claim Requests Claim queue High
IDA-DSP-08 Claim Details Workspace and resolution Critical

Implementation observations requiring UAT confirmation

Observation from implementation Required validation
Dispute dependencies use the settings/ API namespace (settings/disputedependencies, etc.), while categories/titles use dispute/. Confirm the approved endpoints.
The dispute module routes under /disputeresolution/*, while the supplied menu places disputes under Bill Management → Disputes & Adjustments with no matching routes. Confirm the approved menu placement and routes.
Statuses are Pending, Submitted, Under Review, Resolved, Rejected, Closed. Confirm the approved status set.
The Mark Resolved button and the Change Status dropdown update the request status. Confirm the approved resolution path.
The ticket conversation becomes read-only once resolved. Confirm the approved post-resolution behaviour.

IDA-DSP-01 — Dispute categories

Feature overview

The Dispute Categories page at /disputeresolution/category manages category records (add, edit, delete, view).

Preconditions

  • A signed-in administrator.
Field Value
Priority High
Test action Create, edit, and delete a category.
Expected result Category records CRUD with validation and messages.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Test scenarios

Scenario Test steps Expected result Pass/Fail Remarks
List load 1. Open /disputeresolution/category. Categories load with search and status filter. PASS GET dispute/disputecategories.
Add 1. Add a category name and status. A success notification appears. PASS POST dispute/adddisputecategory.
Empty name 1. Save without a name. "Please enter category name" appears. PASS
Edit/Delete 1. Edit and delete a category (confirm). Changes save and deletion confirms. PASS

Tester notes

Record actual result, test data identifiers, device/browser/build, and any variance.

IDA-DSP-02 — Dispute titles

Feature overview

The Dispute Titles page at /disputeresolution/disputetitle manages titles linked to a category.

Preconditions

  • A signed-in administrator with categories.
Field Value
Priority High
Test action Create, edit, and delete a title.
Expected result Titles CRUD with category linkage and validation.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Test scenarios

Scenario Test steps Expected result Pass/Fail Remarks
List load 1. Open /disputeresolution/disputetitle. Titles render with category and status. PASS
Add 1. Add a title, category, and status. A success notification appears. PASS
Validation 1. Save without a title/category/status. "Please enter dispute title" etc. appear. PASS
Delete 1. Delete a title and confirm. The deletion confirms. PASS

Tester notes

Record actual result, test data identifiers, device/browser/build, and any variance.

IDA-DSP-03 — Dependencies

Feature overview

The Dependencies page at /disputeresolution/dependency manages dependency records.

Preconditions

  • A signed-in administrator.
Field Value
Priority High
Test action Create, edit, and delete a dependency.
Expected result Dependencies CRUD with validation.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Test scenarios

Scenario Test steps Expected result Pass/Fail Remarks
List load 1. Open /disputeresolution/dependency. Dependencies render. PASS Uses settings/disputedependencies.
Add 1. Add a dependency name and status. A success notification appears. PASS
Delete 1. Delete a dependency and confirm. The deletion confirms. PASS

Tester notes

Record actual result, test data identifiers, device/browser/build, and any variance.

IDA-DSP-04 — Add dispute

Feature overview

The Add Dispute page at /disputeresolution/adddispute creates a dispute claim request with ratepayer, category/title, related bill, priority, description, and contact details.

Preconditions

  • A signed-in administrator; ratepayers and dispute setup data.
Field Value
Priority Critical
Test action Create a dispute claim request.
Expected result The request is created once and routed to the dispute list.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Test scenarios

Scenario Test steps Expected result Pass/Fail Remarks
Form load 1. Open /disputeresolution/adddispute. The dispute form renders. PASS
Category/title 1. Select a category, then a title. The title list depends on the category. PASS
Details 1. Enter related bill, priority, description, and contact details. Required fields validate. PASS
Submit 1. Submit the request. "Dispute has been created successfully." appears and the user is routed to the dispute list. PASS POST dispute/addclaimrequest.

Tester notes

Record actual result, test data identifiers, device/browser/build, and any variance.

IDA-DSP-05 — Dispute list

Feature overview

The List Dispute page at /disputeresolution/listdispute tracks dispute tickets with search, status, and priority filters.

Preconditions

  • A signed-in administrator with dispute tickets.
Field Value
Priority Critical
Test action Review and filter the ticket list.
Expected result Tickets render with status/priority and open correctly.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Test scenarios

Scenario Test steps Expected result Pass/Fail Remarks
List load 1. Open /disputeresolution/listdispute. Tickets load from dispute/disputes. PASS
Filters 1. Search and filter by status and priority. The list filters. PASS
Open ticket 1. Click a ticket. The user is navigated to the claim details. PASS

Tester notes

Record actual result, test data identifiers, device/browser/build, and any variance.

IDA-DSP-06 — Resolution

Feature overview

The Resolution page at /disputeresolution/resolution lists resolved requests.

Preconditions

  • A signed-in administrator with resolved requests.
Field Value
Priority High
Test action Review the resolved list.
Expected result Resolved requests render.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Test scenarios

Scenario Test steps Expected result Pass/Fail Remarks
List load 1. Open /disputeresolution/resolution. Resolved requests load from dispute/resolvedrequests. PASS

Tester notes

Record actual result, test data identifiers, device/browser/build, and any variance.

IDA-DSP-07 — Claim requests

Feature overview

The Claim Requests page at /disputeresolution/claimrequests is the incoming claim queue.

Preconditions

  • A signed-in administrator with claim requests.
Field Value
Priority High
Test action Review the claim queue.
Expected result Claim requests render.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Test scenarios

Scenario Test steps Expected result Pass/Fail Remarks
Queue load 1. Open /disputeresolution/claimrequests. Claim requests load from dispute/claimrequests. PASS
Open claim 1. Open a claim. The claim details workspace opens. PASS See IDA-DSP-08.

Tester notes

Record actual result, test data identifiers, device/browser/build, and any variance.

IDA-DSP-08 — Claim request details

Feature overview

The Claim Request Details page at /disputeresolution/claimrequests/:id provides a helpdesk workspace with a ticket snapshot, conversation thread, replies, attachments, and status management.

Preconditions

  • A signed-in administrator; a claim in an open or in-review state.
Field Value
Priority Critical
Test action Reply to a claim and change its status.
Expected result Replies are recorded and status changes are reflected; resolved tickets become read-only.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Test scenarios

Scenario Test steps Expected result Pass/Fail Remarks
Details load 1. Open /disputeresolution/claimrequests/{id}. Ticket snapshot, thread, and status render. PASS GET dispute/disputedetails/{id}.
Reply 1. Add a reply with attachments and send. The reply appears in the thread. PASS POST dispute/disputereply.
Change status 1. Use the status dropdown. The status updates. PASS PATCH dispute/changeclaimrequeststatus/{id}.
Mark resolved 1. Click Mark Resolved. The ticket becomes Resolved and the thread read-only. PASS
Read-only resolved 1. Open a resolved ticket. "This ticket is resolved. The thread is read-only…" banner appears. PASS
Not found 1. Open an invalid ID. "Dispute ticket not found." renders. PASS

Tester notes

Record actual result, test data identifiers, device/browser/build, and any variance.