ERP_Distribution/Distribution/docs/testbug.md

Test Bugs & Change Tracker

Running log of backend API failures found during testing and the corresponding frontend changes needed. Add one entry per issue found; move to "Resolved" once fixed and verified.

Open

#	Area	Backend API Failure	Frontend Change Needed	Date
1	Operations → Rides (Create Ride)	On create (not save)	Add a View icon to the action column in Operations → Rides table	2026-09-01
2	Operations → Loading Sheets		Add a View icon to the action column in Operations → Loading Sheets table	2026-09-01
3	Sales (Create Sale)	Sale create not working	Update the Create Sale modal UI	Sale summary calculation not display
4	Orders		Add a View icon to the action column in Orders table	2026-09-01
5	Payments (Record Payment)	Cannot add new payment	Add a View icon to the action column in Payments table	2026-09-01
6	Sales → Visits (Route dropdown)	Selecting a specific route in the route dropdown does not filter route sales — all routes still show; check-in also not working	Fix route filter and check-in on Sales Visits page	2026-09-02
7	Catalogue → Categories (Subcategories)	Added subcategories don't display in the FE	Fix subcategory list rendering	Add a View icon to the action column in Categories table
8	Stock Balances		Add a View icon to the action column in Stock Balances table; allow Edit	2026-09-02
9	Stock Movements	Some rows missing From/To locations — every movement should always have both	Add a View icon and an Edit icon to the action column in Stock Movements table	2026-09-02
10	Procurement → Orders (Place Order)	Placing a new order throws: var userId = currentUser.UserId ?? throw new UnauthorizedAccessException();	Add action icons to the action column in Procurement Orders table	2026-09-02
11	Procurement → GRN		Full module CRUD check pending (CRUD + action icons)	2026-09-02
12	Pricing		Full module CRUD check pending (frontend + CRUD + action icons)	2026-09-02
13	Pricing → Schemes (Add Scheme modal)		Add Scheme modal should show a rule-type-specific "value" input field that changes based on the selected Scheme Name/Rule Type (currently no dynamic value field for the chosen rule type)	2026-09-02
14	Suppliers		Add a View icon and a Cancel icon to the action column in Suppliers table	2026-09-02
15	Driver Profiles	Delete doesn't work	Add a View icon to the action column in Driver Profiles table	2026-09-02
16	Users	Delete action not working	Add View icon	2026-09-02
17	Users → Roles		For now, hide the Add Role icon and the Edit/Cancel (deactivate) icons in the action column; keep only the View icon	2026-09-02
18	Network → Regions	Adding a region that already exists is not blocked — no duplicate-name validation; deleting a region does not work (backend as well)	Add View action icon to the action column; when status is Inactive, region should actually be set to inactive and reflect that status in the frontend	2026-09-02
19	Network → Region Manage		Remove the Rule Config JSON-type field from the frontend view; add a View icon to the action column; on Cancel, just set status to Inactive and reflect that in the UI	2026-09-02
20	Network → Routes	Inactive status doesn't work properly	Check Manage Owner and Manage Stores actions; add View icon to the action column; check Cancel action too	2026-09-02
21	Network → Vehicles		Add a View icon to the action column; check Cancel action	2026-09-02
22	Network → Warehouses	Delete doesn't work	Add a View icon to the action column; check Inactive status	2026-09-02

Resolved

#	Area	Backend API Failure	Frontend Change Needed	Fixed In	Date

Implementation Guide

Cross-cutting rules to apply consistently across every module/page while working through the entries above:

1. Cancel / Delete semantics — Cancel and Delete actions should never remove a row from the page. They should always set the record's status to Inactive (soft delete) and immediately reflect that updated status in the UI. The row must stay visible in the table after the action.
2. Frontend validation — On every page, check that form validation is handled per the actual business scenario (required fields, duplicate checks, valid ranges/formats) before submitting to the backend.
3. Summary calculations — Verify that any summary/total/aggregate calculations shown on a page (e.g. sale totals, stock summaries) compute and display correctly.
4. UI consistency — Maintain consistent layout, spacing, and interaction patterns across all pages.
5. Icon consistency — Use the correct, consistent icon set for actions (View/Edit/Delete/Cancel/etc.) across every page.
6. Search & filters — Check that the search bar and filters actually filter the table results, and that dropdown filters fetch their options correctly from the backend.