Dev-Board End-to-End Validation (Visitor Access HowTo)
Published 2026-10-19
中ENDeveloper end-to-end acceptance steps on the dev board: from simulated visitor booking, scan/call lookup, confirmed opening and result sync to offline failover and backfill after recovery — verify the visitor access chain step by step.
Dev-board end-to-end validation task
For integrating developers: run one complete visitor-access chain on the dev board in order for joint-debug acceptance. Booking, lookup, opening and sync interfaces follow the open-API docs and product manual.
Validation Steps
1. Prepare the dev board and sample project: power on the board, import the sample project, confirm it builds and runs.
2. Simulate visitor booking/call: enter a booking or start a call on the sample side, creating the identity to verify and authorized area.
3. Scan/call triggers lookup: after the visitor scans or calls, the device queries booking and authorized area on the platform or customer system.
4. Confirm authorization and open: after checks pass, open the door and show the result (allowed or denied) on screen.
5. Local log & result sync: write the access record locally and upload the opening result to the customer system.
6. Offline & recovery check: repeat access with the network off — confirm offline recognition and opening, local log; after recovery, confirm records auto-backfill.
Pass Criteria
All six steps return as expected: booking lookupable, authorization accurate, opening matches display, result synced, offline access works and backfill has no gap — acceptance passes.
FAQ
Where is this validation run?
On the dev board with the sample project; run end-to-end in a test space first, then switch to production — do not trial-and-error in production.
What does the offline check cover?
Repeat scan/call access offline: confirm recognition and opening still work, logs are kept locally, and records backfill to the customer system after recovery.
Where are interface fields defined?
This HowTo gives acceptance steps only; booking, lookup, opening and sync fields follow the open-API docs and product manual.