Skip to content

Back Office Menu UAT — Overview and Sidebar Controls

Test series: BO-NAV-01 to BO-NAV-08
Objective: Validate that the Back Office menu is rendered in the left sidebar, follows the supplied hierarchy, and enforces routing and access controls.

Execution ownership

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

Prerequisites: Approved menu configuration, permission matrix, supported browsers, and at least one restricted account per 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
Functional leaf destinations tested 90

Configuration observations requiring UAT confirmation

Observation from supplied menu data Required validation
Rate Fairs uses the internal name Rate Payers. Confirm the approved user-facing label and page heading.
Paid Bills, Partial Paid Bills and Adjust Bills reuse the overdue-arrears slug and permission 178. Confirm that every item has the intended unique route and permission behavior.
Entity Admins uses permission ID 0. Confirm whether this is intentional; verify direct-route and menu visibility controls.
User MGT & Access Controll contains a spelling inconsistency. Confirm the approved wording before release.

Configuration evidence

These observations come from the supplied menu configuration. UAT must determine whether each is an approved alias or a defect; the documentation does not change application permissions or routes.

Coverage summary

Test ID Scenario Priority
BO-NAV-01 Section order and sidebar placement Critical
BO-NAV-02 Expand, collapse and active state High
BO-NAV-03 Role-based visibility Critical
BO-NAV-04 Direct-route enforcement Critical
BO-NAV-05 Route uniqueness Critical
BO-NAV-06 Permission uniqueness and inheritance Critical
BO-NAV-07 Labels and terminology Medium
BO-NAV-08 Responsive and keyboard operation High

BO-NAV-01 — Section order and sidebar placement

Field Value
Priority Critical
Test action Open the Back Office at supported desktop widths and compare the left sidebar order with the approved configuration.
Expected result Analytics, Operations, Financial, Administrative and System Setup appear in priority order in the left sidebar; the menu is not rendered as top navigation.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Tester notes

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

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

Field Value
Priority High
Test action Expand each sidebar level, navigate to a leaf page, refresh, and use browser back/forward.
Expected result Only the intended branches expand; the active item and parent path remain highlighted and usable after navigation or refresh.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Tester notes

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

BO-NAV-03 — Role-based visibility

Field Value
Priority Critical
Test action Compare the sidebar for System Super-Admin and representative restricted roles.
Expected result Each user sees only sections, modules, submodules and menus allowed by the effective permission set.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Tester notes

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

BO-NAV-04 — Direct-route enforcement

Field Value
Priority Critical
Test action Copy an authorized leaf URL and open it with a role that does not have its permission.
Expected result The request is denied safely even when the menu is hidden; no restricted page data or action is exposed.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Tester notes

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

BO-NAV-05 — Route uniqueness

Field Value
Priority Critical
Test action Open every configured leaf and compare the resolved URL, page title and active sidebar item.
Expected result Each distinct menu opens its intended page; duplicate slugs do not redirect multiple business functions to the same unintended screen.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Tester notes

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

BO-NAV-06 — Permission uniqueness and inheritance

Field Value
Priority Critical
Test action Trace section, module, submodule and menu permissions for representative parent/child combinations.
Expected result Permission inheritance is predictable; child access does not exceed parent scope; permission ID 0 or reused IDs are explicitly approved or corrected.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Tester notes

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

BO-NAV-07 — Labels and terminology

Field Value
Priority Medium
Test action Compare displayed labels with approved business terminology, page headings and breadcrumbs.
Expected result Spelling, capitalization and business names are consistent; labels such as Rate Payer/Rate Payers describe the actual destination.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Tester notes

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

BO-NAV-08 — Responsive and keyboard operation

Field Value
Priority High
Test action Use supported viewport widths, browser zoom and keyboard navigation to reach nested menu items.
Expected result The sidebar remains operable without overlap; focus is visible; expanded state and accessible names are announced correctly.
Execution result PASS
Evidence reference Insert link or reference
Defect reference Insert ID or None

Tester notes

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