Complete Manual QA & End-to-End Testing for HotelMantri PMS Web Application
Budget / Salary₹600–1,500
TypeFreelance project
LocationRemote
Posted16 minutes ago
We need an experienced Manual QA Tester for complete end-to-end testing of our HotelMantri PMS web application.
Website:
https://www.hotelmantri.com/
HotelMantri is a cloud-based Hotel Property Management System used for reservations, room operations, housekeeping, finance, reports, channel management, POS, laundry and daily hotel operations.
This is NOT basic website testing. We need complete workflow, data-integrity, role-permission and Super Admin testing.
MODULES TO TEST
- Login / Authentication
- Dashboard
- Operations Board / Room Chart
- Reservations
- Guests
- Housekeeping
- Laundry & Linen
- Finance
- Day Closing
- Reports
- Channel Manager
- Restaurant POS
- Property Settings
- Staff Roles / Permissions
- Multi-property
- Super Admin
RESERVATIONS
Test:
New / Hold / Confirm booking, single & multi-room booking, new/existing guest, modify/cancel, check-in/checkout, room assignment/change, extend stay, early checkout, no-show, partial/full/no advance payment.
Verify:
Nights, rates, tax, discount, total, inventory, guest link, payment, voucher and no duplicate booking.
OPERATIONS & HOUSEKEEPING
Test:
Vacant Clean, Vacant Dirty, Occupied, Cleaning In Progress, Ready for Inspection, Inspected/Ready, Out of Order, Blocked.
Expected flow:
Checkout → Vacant Dirty → Assigned → Cleaning → Inspection → Vacant Clean
ROLE & PERMISSION TESTING
Test:
Owner, Manager, Reception, Accounts, Housekeeping.
Direct URL access must also be tested.
Example:
Housekeeping user must not access Finance, Reports, Rates, Channel Manager, Settings or User Management.
FINANCE
Verify Revenue, Collection and Outstanding separately.
Example:
Room Bill ₹5,000
Cash ₹2,000
UPI ₹1,000
Expected:
Revenue ₹5,000
Collection ₹3,000
Outstanding ₹2,000
Test:
Cash, UPI, Card, Bank, OTA, Agent, Corporate.
Verify:
No duplicate revenue/collection, correct outstanding, correct expenses and correct cash closing.
Cash Closing:
Opening Cash
+ Cash Collection
- Cash Expense
- Approved Cash Outflow
= System Closing Cash
DAY CLOSING & REPORTS
Test closing validations and verify:
Daily Report, MTD, YTD, Cash Closing, Dashboard, Occupancy, ARR, RevPAR, Revenue, Collection, Expense, Outstanding and GST summary where applicable.
If reopen exists, reopening/reclosing must not duplicate data.
LAUNDRY & LINEN
Test stock, dispatch, partial receive, pending, damaged/lost, billing and vendor payment.
Example:
Sent 50
Received 49
Expected Pending 1
Billing should apply only to received/billable quantity.
POS
If enabled, test:
New order, KOT, table order, billing, payment, discount, cancel/void and POS revenue integration.
CHANNEL MANAGER
Where safe test/staging access is provided, test:
- Room mapping
- Rate plan mapping
- Inventory
- Rates
- Stop Sell
- Restrictions
- New / modified / cancelled booking
- Duplicate prevention
- Failed sync
- Retry
- Sync logs
Do not perform risky live OTA changes without approval.
SUPER ADMIN
Test:
- Super Admin login
- Property creation/edit
- Property activation/deactivation
- User creation
- User activation/deactivation
- Role assignment
- Password reset
- Property-wise access
- Module enable/disable if available
- Subscription/plan controls if available
- Multi-property management
- Global settings
- Audit/admin actions
PROPERTY ISOLATION / SECURITY
Verify:
- Hotel A cannot access Hotel B data
- Normal users cannot access Super Admin
- Direct Super Admin URLs are blocked
- Changing IDs/URLs must not expose another hotel’s data
- Staff cannot accidentally gain Super Admin rights
- Disabled users/properties lose access correctly
- Super Admin changes affect only the correct property
- No cross-property reservation, guest, finance or report leakage
Cross-property data leakage or privilege escalation = Critical severity.
NEW PROPERTY FLOW
Create a test property from Super Admin and verify:
Property → Room Categories → Rooms → Users → Roles → Settings → Operations Board → Housekeeping → Finance → Reports → Channel Manager setup → POS/Laundry if enabled.
New property must start with isolated and correct data.
DATA INTEGRITY
Very important:
Create Reservation
→ Inventory updates
→ Guest updates
→ Operations Board updates
→ Payment updates Finance
→ Reports update
One transaction must NOT create duplicate records.
Also test:
Save → Refresh → Logout → Login again
Data must remain correct.
NEGATIVE / EDGE CASES
Test:
Double-click Save, repeated Confirm, refresh during save, internet interruption, multiple tabs, invalid dates, checkout before check-in, zero rate, large values, empty required fields, invalid mobile/email, duplicate guest, duplicate booking, session expiry and browser back button.
UI / UX / RESPONSIVE
Check:
Broken layouts, overlap, text clipping, spacing, font size, buttons, error messages, loading states, mobile/tablet usability, horizontal scroll, forms, tables and modals.
CROSS-BROWSER
Test latest versions where possible:
Chrome, Edge, Firefox, Safari.
PERFORMANCE
Record slow areas:
Login, Dashboard, Operations Board, Reservation save, Finance and Reports.
DELIVERABLES
Every bug must include:
Bug ID
Module
Title
Severity
Priority
Environment
Preconditions
Steps to Reproduce
Expected Result
Actual Result
Screenshot / Video
Status
Severity:
Critical
High
Medium
Low
FINAL DELIVERY
1. Test Case / Scenario Document
2. Complete Bug Report
3. Screenshots / Screen Recordings
4. Browser / Device Coverage
5. Passed / Failed Summary
6. Retesting after developer fixes
7. Final QA Summary
8. Remaining Open Issues
IMPORTANT
We do not need only visual/button testing.
We need someone who can understand connected hotel workflows and verify data accuracy across modules.
Please answer:
1. Have you tested PMS, ERP, booking/reservation or transactional SaaS before?
2. How would you test reservation → inventory → finance → reports without duplication?
3. Can you perform role/permission and Super Admin testing?
4. Which devices/browsers can you test?
5. Can you share a sample bug report/test case?
6. Mention timeline for first testing cycle and retesting.
Website:
https://www.hotelmantri.com/
HotelMantri is a cloud-based Hotel Property Management System used for reservations, room operations, housekeeping, finance, reports, channel management, POS, laundry and daily hotel operations.
This is NOT basic website testing. We need complete workflow, data-integrity, role-permission and Super Admin testing.
MODULES TO TEST
- Login / Authentication
- Dashboard
- Operations Board / Room Chart
- Reservations
- Guests
- Housekeeping
- Laundry & Linen
- Finance
- Day Closing
- Reports
- Channel Manager
- Restaurant POS
- Property Settings
- Staff Roles / Permissions
- Multi-property
- Super Admin
RESERVATIONS
Test:
New / Hold / Confirm booking, single & multi-room booking, new/existing guest, modify/cancel, check-in/checkout, room assignment/change, extend stay, early checkout, no-show, partial/full/no advance payment.
Verify:
Nights, rates, tax, discount, total, inventory, guest link, payment, voucher and no duplicate booking.
OPERATIONS & HOUSEKEEPING
Test:
Vacant Clean, Vacant Dirty, Occupied, Cleaning In Progress, Ready for Inspection, Inspected/Ready, Out of Order, Blocked.
Expected flow:
Checkout → Vacant Dirty → Assigned → Cleaning → Inspection → Vacant Clean
ROLE & PERMISSION TESTING
Test:
Owner, Manager, Reception, Accounts, Housekeeping.
Direct URL access must also be tested.
Example:
Housekeeping user must not access Finance, Reports, Rates, Channel Manager, Settings or User Management.
FINANCE
Verify Revenue, Collection and Outstanding separately.
Example:
Room Bill ₹5,000
Cash ₹2,000
UPI ₹1,000
Expected:
Revenue ₹5,000
Collection ₹3,000
Outstanding ₹2,000
Test:
Cash, UPI, Card, Bank, OTA, Agent, Corporate.
Verify:
No duplicate revenue/collection, correct outstanding, correct expenses and correct cash closing.
Cash Closing:
Opening Cash
+ Cash Collection
- Cash Expense
- Approved Cash Outflow
= System Closing Cash
DAY CLOSING & REPORTS
Test closing validations and verify:
Daily Report, MTD, YTD, Cash Closing, Dashboard, Occupancy, ARR, RevPAR, Revenue, Collection, Expense, Outstanding and GST summary where applicable.
If reopen exists, reopening/reclosing must not duplicate data.
LAUNDRY & LINEN
Test stock, dispatch, partial receive, pending, damaged/lost, billing and vendor payment.
Example:
Sent 50
Received 49
Expected Pending 1
Billing should apply only to received/billable quantity.
POS
If enabled, test:
New order, KOT, table order, billing, payment, discount, cancel/void and POS revenue integration.
CHANNEL MANAGER
Where safe test/staging access is provided, test:
- Room mapping
- Rate plan mapping
- Inventory
- Rates
- Stop Sell
- Restrictions
- New / modified / cancelled booking
- Duplicate prevention
- Failed sync
- Retry
- Sync logs
Do not perform risky live OTA changes without approval.
SUPER ADMIN
Test:
- Super Admin login
- Property creation/edit
- Property activation/deactivation
- User creation
- User activation/deactivation
- Role assignment
- Password reset
- Property-wise access
- Module enable/disable if available
- Subscription/plan controls if available
- Multi-property management
- Global settings
- Audit/admin actions
PROPERTY ISOLATION / SECURITY
Verify:
- Hotel A cannot access Hotel B data
- Normal users cannot access Super Admin
- Direct Super Admin URLs are blocked
- Changing IDs/URLs must not expose another hotel’s data
- Staff cannot accidentally gain Super Admin rights
- Disabled users/properties lose access correctly
- Super Admin changes affect only the correct property
- No cross-property reservation, guest, finance or report leakage
Cross-property data leakage or privilege escalation = Critical severity.
NEW PROPERTY FLOW
Create a test property from Super Admin and verify:
Property → Room Categories → Rooms → Users → Roles → Settings → Operations Board → Housekeeping → Finance → Reports → Channel Manager setup → POS/Laundry if enabled.
New property must start with isolated and correct data.
DATA INTEGRITY
Very important:
Create Reservation
→ Inventory updates
→ Guest updates
→ Operations Board updates
→ Payment updates Finance
→ Reports update
One transaction must NOT create duplicate records.
Also test:
Save → Refresh → Logout → Login again
Data must remain correct.
NEGATIVE / EDGE CASES
Test:
Double-click Save, repeated Confirm, refresh during save, internet interruption, multiple tabs, invalid dates, checkout before check-in, zero rate, large values, empty required fields, invalid mobile/email, duplicate guest, duplicate booking, session expiry and browser back button.
UI / UX / RESPONSIVE
Check:
Broken layouts, overlap, text clipping, spacing, font size, buttons, error messages, loading states, mobile/tablet usability, horizontal scroll, forms, tables and modals.
CROSS-BROWSER
Test latest versions where possible:
Chrome, Edge, Firefox, Safari.
PERFORMANCE
Record slow areas:
Login, Dashboard, Operations Board, Reservation save, Finance and Reports.
DELIVERABLES
Every bug must include:
Bug ID
Module
Title
Severity
Priority
Environment
Preconditions
Steps to Reproduce
Expected Result
Actual Result
Screenshot / Video
Status
Severity:
Critical
High
Medium
Low
FINAL DELIVERY
1. Test Case / Scenario Document
2. Complete Bug Report
3. Screenshots / Screen Recordings
4. Browser / Device Coverage
5. Passed / Failed Summary
6. Retesting after developer fixes
7. Final QA Summary
8. Remaining Open Issues
IMPORTANT
We do not need only visual/button testing.
We need someone who can understand connected hotel workflows and verify data accuracy across modules.
Please answer:
1. Have you tested PMS, ERP, booking/reservation or transactional SaaS before?
2. How would you test reservation → inventory → finance → reports without duplication?
3. Can you perform role/permission and Super Admin testing?
4. Which devices/browsers can you test?
5. Can you share a sample bug report/test case?
6. Mention timeline for first testing cycle and retesting.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.