Testing Scenarios for PoolCar
Please follow these instructions for testing scenarios for PoolCar
Testing Scenarios for PoolCar Customers | General User | Pool Officer | Pool Manager | Sysadmin |
|---|---|---|---|---|
👥 User Access & Authentication |
|
|
|
|
User AccountsAll relevant users (drivers and admins) have been created/imported successfully. | ||||
SSO (if enabled)Users can log in via the customer’s identity provider and access PoolCar without credential errors. | ||||
Roles & PermissionsRoles are correctly assigned (e.g. General User, Pool Administrator), with appropriate access to menus, vehicles, and business units. |
|
|
| |
New User ExperienceFirst-time users can self-register (if enabled) and receive onboarding instructions or email confirmations. |
|
| ||
🗓️ Vehicle Management & Scheduling |
|
|
|
|
Vehicle VisibilityVehicles are assigned to correct pools / access groups and visible to appropriate users. | ||||
Vehicle StatusStatus reflects real-time availability (Available, Booked, Maintenance booking, etc.) | ||||
ServicingServicing schedules are in place and flagged when due. | ||||
Location-Based BookingVehicles can be filtered by location or depot, and rules are enforced for location-specific access. | ||||
🚗 Bookings & Workflow |
|
|
|
|
Booking ProcessUsers can create, view, and cancel bookings via web and/or mobile interface. | ||||
Approval Workflow (if enabled)Bookings trigger the appropriate approval chain and approvers are notified correctly. | ||||
Key CollectionBooking and vehicle information matches across PoolCar and (if applicable) KeyMaster. | ||||
Booking NotificationsEmail confirmations, reminders, and overdue notices are received as expected. | ||||
Booking RestrictionsBooking rules (e.g. vehicle type, location, licence class) are enforced based on configuration. | ||||
🔐 Integration with KeyMaster (if applicable) |
|
|
|
|
Booking SyncPoolCar bookings sync to KeyMaster cabinets and match expected vehicle/key allocations. |
|
|
| |
Key Access ControlOnly valid bookings are allowed to collect/return keys via cabinet. |
|
| ||
Logs & AuditsBooking and key activity is logged and visible in PoolCar audit trail. |
|
|
| |
📄 Reporting & Auditability |
|
|
|
|
Booking HistoryAll past bookings are logged with correct vehicle, user, time, and status. | ||||
ReportsKey reports are accessible and accurate. | ||||
ExportingBooking or fleet data can be exported to .csv or .xls format as required. | ||||
System LogsAudti trail capture relevant events (logins, cancellations, approvals). | ||||
⚙️ System Settings & Configuration |
|
|
|
|
Business Unit StructureOrganisational hierarchy and business units are accurately configured. | ||||
Licence Management & VerificationDrivers must have valid licence information (and verification workflow is defined) | ||||
Terms & ConditionsBooking declarations or policies are visible and accepted before booking. | ||||
NotificationsSystem-wide email templates and triggers are working and reflect agreed wording. |
|
|
| |
Operating Hours & HolidaysLocalisation is set based on organisation working hours | ||||
🧾 Customer Confirmation |
|
|
|
|
Users can log in and make bookings successfully Bookings follow correct workflow and trigger notifications Vehicles and business units are accurately configured Reports show expected data KeyMaster (if applicable) integration is functional Booking restrictions and policies are enforced All test bookings have been verified and cancelled |
|
|
|