QA context from my CV
Hello Palika includes News, Notices, Events, Appointment, Complaint, Invitation, Decision Management, Active Officer Status, notification, and Municipal Development Plan modules. That makes it a strong QA case for visibility rules, public content accuracy, form validation, and role-based workflows.
Risk & proposed scope
The highest-risk areas are incorrect public information, complaints disappearing after submission, appointments showing wrong status, and notifications sent to the wrong audience. The proposed scope covers one municipality admin, one officer, and one citizen account.
Example test scenarios
- Publish a notice as draft, private, scheduled, and public; verify citizen visibility for each state.
- Submit a complaint with required and optional fields; confirm tracking status and stored evidence.
- Change active officer availability; verify the public status updates without stale information.
- Publish a decision and confirm it is accessible from the intended public page only.
- Send a targeted notification and verify audience, timing, and content.
Evidence & release criteria
Evidence should include role, module, record ID, visibility state, timestamp, notification target, and screenshot or API response where possible. Release criteria should block incorrect public publication, lost complaint records, and wrong-recipient notifications.