Skip to content

iDARMS Frontend (Back Office) — Overview and Sidebar Controls

Test series: IDA-NAV-01 to IDA-NAV-08
Objective: Validate that the Back Office sidebar renders the supplied menu hierarchy, that the registered routes resolve to the implemented pages, and that protected routes enforce authentication.

Execution ownership

Recommended owners: System Super-Admin; Security/Access administrator; representative business users

Prerequisites: Approved menu configuration (/sys/usermenu), supported browsers, and controlled test accounts for each business area.

Execution control

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

Supplied menu inventory

Configuration level Count
Sidebar sections 5
Modules 12
Submodules 41
Explicit menu entries 67

The five sections render in order: Analytics → Operations → Financial → Administrative → System Setup. The sidebar is server-driven from the /sys/usermenu endpoint; the active menu leaves link to /module/… routes that resolve to the page components documented in the module pages of this series.

Implemented modules and series

Module page Test series Scope
Authentication IDA-AUTH Login, OTP, password recovery, session
Dashboard IDA-DSH Operational/financial dashboard widgets
Property Management IDA-PRP Property lifecycle and workflows
Rate Payer Information IDA-RTP Ratepayer registration and lists
GIS Mapping IDA-GIS Property map and filters
Communication IDA-COM Email/SMS/bulk/push/WhatsApp/templates
Bill Management IDA-BIL Bill lists, details and payment
Payment Management IDA-PAY Payment history, details, receipts
Accounting & Finance IDA-ACC Chart of accounts, journals, reports
Dispute Resolution IDA-DSP Dispute setup, tickets, claim requests
Entity Management IDA-ENT Entity CRUD, hierarchy, map, admins
Block Management IDA-BLK Block list and add/edit
User Management IDA-USR Users, roles, partners, audit logs
System Setup IDA-SET Rates, categories, divisions, zones, LVD
Account Settings IDA-PRO Profile and password

Configuration observations requiring UAT confirmation

Observation from menu/routes Required validation
Financial Dashboard has a registered route (/financialdashboard) but is not present in the /sys/usermenu response; both dashboards render the same Dashboard component. Confirm whether Financial Dashboard is in scope and intended to be identical.
The Dispute Resolution module is implemented under /disputeresolution/*, while the supplied menu lists disputes under Financial → Bill Management → Disputes & Adjustments (billmanagement/disputesadjustments/*) with no matching routes. Confirm the approved menu placement and routes for dispute screens.
Bill Generation, Bill Delivery, and Reports & Audit submodules in the menu have no registered routes (Auto Jobs Status, On-Demand Bill, Bulk Bill Run Logs, Issue/Re-Issue Bills, Delivery Logs, Billing Reports, Collection Reports, Ageing & Arrears, Bill Audit Log). Confirm whether these destinations are expected to resolve.
USSD Management appears in the menu and has a route constant, but no route is registered in the router. Confirm whether USSD screens are in scope.
Several implemented routes are not in the menu (e.g., merge/split pages, /settings/addblock, expense/budget/tax/audit reports, /profile). Confirm whether these should be exposed via the sidebar.
The menu uses the internal name Rate Payers (label "Rate Fairs") and the spelling User MGT & Access Controll. Confirm the approved user-facing labels.
Paid Bills, Partial Paid Bills and Adjust Bills reuse the same slug/permission as Overdue & Arrears. Confirm that each item has the intended unique route and permission behavior.

IDA-NAV-01 — Section order and sidebar placement

Feature overview

The left sidebar renders the five menu sections in the supplied order, with modules, submodules, and menu leaves nested beneath each section.

Preconditions

  • A signed-in System Super-Admin at supported desktop widths.
Field Value
Priority Critical
Test action Open the Back Office and compare the left sidebar with the supplied menu configuration.
Expected result Analytics, Operations, Financial, Administrative and System Setup appear in order; nested items match the configuration.
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
Section order 1. Sign in and inspect the sidebar. Sections appear as Analytics, Operations, Financial, Administrative, System Setup. PASS
Module nesting 1. Expand each section. Modules match the supplied 12-module inventory. PASS
Menu leaves 1. Expand each submodule. Menu entries resolve to the expected /module/… links. PASS
Loading skeleton 1. Reload and observe the sidebar. A loading skeleton is shown until /sys/usermenu returns. PASS
Logo 1. Inspect the sidebar header. The iDARMS logo links to /. PASS

Tester notes

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

IDA-NAV-02 — Expand, collapse and active state

Feature overview

Sidebar branches expand and collapse, and the active leaf and its parent path remain highlighted after navigation and refresh.

Preconditions

  • A signed-in user with access to nested menu branches.
Field Value
Priority High
Test action Expand branches, navigate to a leaf, refresh, and use browser back/forward.
Expected result Only the intended branches expand; the active item and parent path stay highlighted and usable.
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
Expand/collapse 1. Click each expandable module/submodule. Only the clicked branch opens/closes. PASS
Active state 1. Open a leaf page. The leaf and its parent chain are highlighted. PASS
Refresh 1. Refresh a leaf page. The active state is restored. PASS
Back/forward 1. Navigate between leaves and use browser history. The sidebar tracks the current location. PASS

Tester notes

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

IDA-NAV-03 — Role-based visibility

Feature overview

Each user sees only the sections, modules, submodules, and menus permitted by their role.

Preconditions

  • At least one restricted role account per business area.
Field Value
Priority Critical
Test action Compare the sidebar for the Super-Admin and representative restricted roles.
Expected result Each user sees only items allowed by the effective permission set.
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
Super-Admin menu 1. Sign in as Super-Admin. All 5 sections are visible. PASS
Restricted role 1. Sign in as a restricted role. Only permitted items render. PASS
Permission 0 item 1. Check Entity Admins visibility. Confirm behavior for the item with permission ID 0. PASS See observations.

Tester notes

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

IDA-NAV-04 — Direct-route enforcement

Feature overview

Pages can be reached by URL even when the menu is hidden; the application protects every module route with the authentication wrapper.

Preconditions

  • A valid session and access to module URLs.
Field Value
Priority Critical
Test action Open implemented module URLs directly and confirm each renders its page.
Expected result Every registered route renders the intended page; unauthenticated access is redirected to login.
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
Module URL 1. Open /entity/entities directly. The All Entities page renders. PASS
Signed-out access 1. Sign out and open a protected URL. The user is redirected to /auth/login. PASS
404 route 1. Open an unknown URL. The 404 page renders. PASS
Menu-only items 1. Open a menu item without a registered route (e.g. billmanagement/billgeneration/autojobsstatus). The 404 page renders. PASS See observations.

Tester notes

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

IDA-NAV-05 — Route uniqueness

Feature overview

Distinct menu items resolve to distinct implemented pages; duplicate slugs are identified for confirmation.

Preconditions

  • A signed-in user able to open every implemented leaf.
Field Value
Priority Critical
Test action Open every implemented leaf and compare URL, title, and active sidebar item.
Expected result Each distinct item opens its intended page; duplicates do not redirect to unintended screens.
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
Paid/Partial/Adjust 1. Open Paid, Partial Paid and Adjust Bills. Confirm whether each shows its own branded list or the same Overdue screen. PASS Slug reuse; see observations.
Settings lists 1. Open the Division/Block/Zone add and list URLs. Each list/add route renders the expected shared page with the correct mode. PASS

Tester notes

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

IDA-NAV-06 — Labels and terminology

Feature overview

Displayed labels match approved business terminology and page headings.

Preconditions

  • A signed-in user with access to all sections.
Field Value
Priority Medium
Test action Compare displayed labels with page headings and breadcrumbs.
Expected result Spelling and capitalization are consistent across menu, heading, and breadcrumb.
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
Module names 1. Inspect menu labels. "User MGT & Access Controll" and "Rate Payers" wording is confirmed. PASS See observations.
Breadcrumbs 1. Open several pages. Breadcrumbs match the menu path. PASS Some pages reuse copied copy (e.g., settings pages).

Tester notes

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

IDA-NAV-07 — Responsive and keyboard operation

Feature overview

The sidebar remains usable at supported widths and with keyboard navigation.

Preconditions

  • Supported viewport widths and a keyboard.
Field Value
Priority High
Test action Resize, zoom, and use the keyboard to reach nested menu items.
Expected result The sidebar stays operable without overlap; focus is visible.
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
Compact widths 1. Resize to 1400px and below. The sidebar remains usable without overlap. PASS
Keyboard 1. Tab through the menu. Focus is visible and leaves are reachable. PASS
Support/Logout card 1. Inspect the sidebar footer. Support and Logout controls render (collapsed state shows a logout icon). PASS

Tester notes

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

IDA-NAV-08 — Menu-to-module traceability

Feature overview

Each implemented page documented in this series is traceable to its menu path, route, and test series.

Preconditions

  • The completed module pages of this series.
Field Value
Priority High
Test action Trace each documented feature to its route and menu path.
Expected result Every implemented feature has a stable test ID and route reference.
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
Series trace 1. Review the module pages in this series. Test IDs and routes are consistent. PASS
Cross-reference 1. Compare with the existing Back Office BO-* destination series. The IDA module series complements the BO destination series. PASS

Tester notes

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