Integration checks
Run these checks for every target deployment and client platform, covering normal use, permission denial, network failures and cleanup.
| Scenario | Expected result |
|---|---|
| Register teacher and student | Two distinct eduUserId values mapped to business users |
| Create classroom | Valid schedule, returned classroomId, end derived from duration |
| Non-member enters invite_only classroom | Rejected; a teacher token hint does not bypass membership |
| Two accounts enter one classroom | Required domains ready; members, chat and class state agree |
| Teacher starts / student leaves / teacher ends | Classroom state, individual connection and whole-class state change respectively |
| Grant/deny camera and microphone | Actual callbacks determine device state; denial has clear feedback |
| Revoke whiteboard/chat/device permission | Actions follow effective permissions; open devices can still be closed |
| Late join and network recovery | Restore authoritative backend/whiteboard state without duplicates |
| Token expiry | Backend authenticates and reissues; a new instance uses the new token |
| Close and re-enter | Resources/subscriptions released, no leftover capture or duplicate callbacks |
| Web production build / native release build | Assets, WASM, native libraries and architectures match |
Record SDK/server versions, OS/browser, device architecture and failure traces. See the platform guides for mini program, HarmonyOS and native Windows environment requirements.
Server webhooks
After configuring callbacks, verify signed start/end events, body tampering, expired signature timestamps, duplicates, HTTP 500 and timeouts. Confirm that (appId, eventId) deduplication survives service restarts and acknowledgments occur only after durable persistence.
Privacy and collection
Complete the privacy integration checks. Verify host camera/microphone descriptions, actual requests and storage before consent and after refusal/withdrawal, capture shutdown on exit, provider inventories and deletion procedures. The data inventory must match the installed version and enabled features.