Testing Scenarios for SSO Customers

Users

Login

(A user within the Customer’s domain will be able to sign into PoolCar from their Azure AD log in page and be redirected to the Welcome page (at first time log ins) or the default page - New Booking or My Bookings (for future log ins))

Register via Welcome Page

(When logging in for the first time the User will have their required attributes pre-populated on the Welcome page)

All existing Sysadmins will retain their admin roles after the integration is turned on. Smartrak support team will be on hand to grant this role if it has not migrated across.

Check driver register is updated

Check email notifications (emails may be disabled in UAT)

Vehicles & Pools

Add a new vehicle

Edit vehicle information

Assign to a Pool

Unassign from a Pool

Archive vehicle (check count against Vehicle Register)

Test bulk import of vehicles

Bookings

If any bookings were created before SSO was implemented, a user should be able to access any previously created bookings

Create a booking

Book on behalf process (if enabled)

Edit a booking

Delete a booking

Check approval triggers (if using)

Check Out / In

(depending on which process is used)

Via KeyMaster

Via Check In / Out board

Via Manual check in/out via mobile site/app

Via automated geofence check out/in

Reporting & APIs

Internal Charging report

Logbook report

APIs

Emails

Check System Generated Emails (Email Log)

note that emails might be disabled in the UAT instance

Audit Trail

Check the Audit Trail to ensure the flow of data