Testing Scenarios for Smartrak Admin/app (AVL, Nextrak, OBD)
Please follow these instructions to test the connection of telematics devices to Smartrak Admin and Smartrak app (map/reporting/insights/dashboard/fleet servicing)
- 1 Testing Scenarios for Smartrak Admin & app
- 1.1 🔌 Device Installation & Connectivity
- 1.1.1 Device Installation
- 1.1.2 Device Connection
- 1.1.3 Power Management
- 1.1.4 GPS Fix
- 1.2 📡 Trip Data & Event Capture
- 1.2.1 Trip Recording
- 1.2.2 Idle Detection
- 1.2.3 CAN Data (if applicable)
- 1.2.4 Ignition Events
- 1.3 🗺️ Tracking & Mapping
- 1.3.1 Live Tracking
- 1.3.2 Route History
- 1.3.3 Alerting (if applicable)
- 1.3.4 Location Accuracy
- 1.4 🛠️ Portal & Reporting Functionality
- 1.4.1 Vehicle Assignment
- 1.4.2 Trip Visibility
- 1.4.3 Driver ID (if configured)
- 1.4.4 Scheduled Reports
- 1.4.5 Fleet Servicing (if configured)
- 1.4.6 Alert Functionality
- 1.4.7 User Access
- 1.4.8 Data Retention
- 1.5 🔒 Security & Privacy
- 1.5.1 Data Access Control
- 1.5.2 Privacy Controls
- 1.1 🔌 Device Installation & Connectivity
Testing Scenarios for Smartrak Admin & app | Map User | Client Admin |
|---|---|---|
🔌 Device Installation & Connectivity |
|
|
Device InstallationTelematics devices (OBD II / AVL / Nextrak) are physically installed and assigned to the correct vehicles. |
| |
Device ConnectionDevices are showing as online and communicating with the platform within expected timeframes (e.g. connected within 5 minutes of ignition). |
| |
Power ManagementDevices remain powered correctly when the vehicle is in use and follow expected sleep/wake behaviour. |
| |
GPS FixGPS is acquired quickly after key on, with consistent signal during trips. |
| |
📡 Trip Data & Event Capture |
|
|
Trip RecordingTrips are captured with accurate start/end times, durations, and distances. |
| |
Idle DetectionIdling events are accurately recorded when the vehicle is stationary with key on (based on default threshold of 2 minutes). |
| |
CAN Data (if applicable)Engine diagnostics (EV battery level, range, charging status) are available and accurate from supported vehicles. |
| |
Ignition EventsKey on/off events are correctly logged, without false positives or missed data. |
| |
🗺️ Tracking & Mapping |
|
|
Live TrackingVehicles display on the live map with current location and status (key on/off, speed). |
| |
Route HistoryTrips are visible in the trip history with correct paths drawn, no significant GPS drift. |
| |
Alerting (if applicable)Device triggers accurately on the map as well as alerts sent to correct receipients Vehicles trigger entry/exit alerts on configured geofences |
| |
Location AccuracyGPS data falls within expected tolerance (Minimum Position Accuracy). |
| |
🛠️ Portal & Reporting Functionality |
|
|
Vehicle AssignmentDevices are correctly linked to the appropriate vehicles and visible in Smartrak app. | ||
Trip VisibilityUsers can access trip data via Smartrak app or relevant reports. |
| |
Driver ID (if configured)Drivers are correctly linked via key use, PoolCar bookings, or iButton/driver ID (if implemented). | ||
Scheduled ReportsAutomated reports (e.g. trip reports, idle reports) are delivered on schedule and with correct data. | ||
Fleet Servicing (if configured)Fleet servicing alerts are configured and being received. Compliance alerts for NZ customers are being updated automatically (when in alert period) via NZTA API |
| |
📋 Compliance & Alerts |
|
|
Alert FunctionalityAlerts for speeding, harsh braking, ignition after hours etc. are triggered according to rules. | ||
User AccessRelevant staff can view, export or subscribe to alert and event data. |
| |
Data RetentionTrip and event data is retained per contractual agreement (2.5 years/913 days rolling). |
| |
🔒 Security & Privacy |
|
|
Data Access ControlOnly authorised users can access vehicle/driver data in the Smartrak app. |
|
|
Privacy ControlsRestricted access is configured where required.
|
| |
🧾 Customer Confirmation |
|
|
All installed vehicles are reporting live data Trip data appears accurately in Smartrak app Alerts tested and received Access for required staff confirmed Test period (5-10 working days) shows stable and accurate data Any issues raised during UAT have been resolved or documented with agreed timelines |