Skip to content

iDARMS Frontend (Back Office) — Block Management Module Acceptance Tests

Test series: IDA-BLK-01 to IDA-BLK-02
Objective: Validate that geographic blocks can be listed and added or edited through the Back Office.

Execution ownership

Recommended owners: System Super-Admin; GIS/Property business owner

Prerequisites: A signed-in administrator, an MMDA, and a controlled UAT environment.

Execution control

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

Feature overview

The Block Management module covers:

  • Block List at /entity/listblock.
  • Add/Edit Block at /entity/addblock and /entity/editblock/{id}, with polygon coordinates captured via a map picker.

Coverage summary

Test ID Feature Scenario Priority
IDA-BLK-01 Block List List, search and open Critical
IDA-BLK-02 Add/Edit Block Create and update Critical

Implementation observations requiring UAT confirmation

Observation from implementation Required validation
Blocks are managed under the Entity Management module in the menu (entity/block), while the frontend implements them in the blocks module at /entity/*block*; the System Setup routes /settings/addblock reuse a separate component. Confirm the approved module placement.
The block form uses a Google Map area picker for coordinates; a separate unused MapPlotSelection helper exists. Confirm the approved coordinate capture.
Edit and Delete row actions: Edit is enabled, Delete is present in the menu. Confirm the approved row actions.

IDA-BLK-01 — Block list

Feature overview

The Block List at /entity/listblock lists blocks with search filters and server pagination.

Preconditions

  • A signed-in administrator with seeded blocks.
Field Value
Priority Critical
Test action Review the list, search, and open a block.
Expected result Blocks render with MMDA, region, coordinates, and status.
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 /entity/listblock. Blocks load from /entity/blocks. PASS
Columns 1. Inspect the table. Block Name, Block Number, MMDA, Region, Coordinates, Status, and Actions render. PASS
Filters 1. Use MMDA, Block Name, and Status filters. The list filters and the URL updates. PASS
Pagination 1. Change page size or jump pages. Pagination works. PASS
Open block 1. Open the edit action. The user is navigated to /entity/editblock/{id}. PASS

Tester notes

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

IDA-BLK-02 — Add/edit block

Feature overview

The Add/Edit Block pages capture the MMDA, block name, number, status, and polygon coordinates.

Preconditions

  • A signed-in administrator; an MMDA and polygon coordinates.
Field Value
Priority Critical
Test action Create a block, then edit it.
Expected result The block is created once with the captured polygon; updates save.
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
Add block 1. Open /entity/addblock.
2. Enter block name and status, select MMDA and coordinates.
Success notification appears and the list opens. PASS POST /entity/addblock.
Required name 1. Save without a block name. The required-field error appears. PASS
Edit block 1. Open /entity/editblock/{id} and update. Changes save. PASS PATCH /entity/updateblock/{id}.

Tester notes

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