Recorded browser self-test
Browser self-test
This page exercises the real SavyScan SDK 0.5.0-beta.7 bundle, OpenCV processor, image correction, editing controls, and multipage PDF callback in the browser you opened.
Live result
Photo-workflow qualification
Preparing the browser suite…
01 / Browser record
Evidence captured by this run
- SDK
- Loading…
- Run time
- —
- Platform
- —
- Browser identifier
- —
- Viewport
- —
- Runtime / self-test capabilities
- Checking…
- Camera boundary
- This page temporarily replaces getUserMedia with a deterministic denial during each run and restores it afterward, so the self-test cannot request camera hardware.
02 / Browser self-test
Public integration checks
Each check uses the customer-facing browser bundle and SDK-owned interface. The self-test does not use SavyScan.testing, send document data anywhere, or claim to be a CI automation gate.
03 / Evidence boundary
What a passing run means
Established here. This browser can load the pinned runtime and WebAssembly processor, enforce structured configuration errors, import generated JPEGs, crop, rotate, assemble two corrected pages, return a structurally checked two-page PDF Blob, reopen, cancel, restore host focus/scroll/inert state, and remove the SDK-owned interface.
Still requires physical testing. Camera permissions, live preview, automatic/manual camera capture, focus quality, touch corner dragging, orientation changes, background/restore, mobile memory pressure, host upload, and email attachment behavior are outside this recorded browser self-test.
The retained result is published as a machine-readable record bound to exact SHA-256 asset digests. A fresh live run does not alter that checked-in record.