There's a gap between
building and shipping
AR/VR products.
Most AR/VR issues surface after deployment — not before. Selmurat's process closes that gap by running structured validation before a build reaches users.
Each phase produces a concrete artifact — not just a status update. The sequence is fixed because order matters in XR debugging.
Intake & Scope
The build is reviewed against the project brief. Scope boundaries are set before any device is powered on.
Environment Configuration
Hardware profiles are matched to target deployment conditions — headset firmware, tracking mode, render pipeline, and scene complexity all documented before testing begins.
- Device matrix defined
- Render settings logged
- Baseline performance captured
Functional Testing
Interaction flows are tested against defined acceptance criteria. Spatial anchoring, controller mapping, and gaze-input accuracy are each verified independently.
- Interaction path coverage
- Anchor drift measurement
- Input latency recording
Bug Isolation
Each defect is reproduced in isolation. Root cause is documented separately from symptom to prevent misclassification during fixes.
Performance Profiling
Frame rate stability, memory allocation, and thermal behaviour are measured across minimum and maximum load scenarios. Results are compared against platform targets, not internal benchmarks.
- Frame pacing analysis
- GPU/CPU load mapping
- Thermal ceiling check
Verification & Sign-off
Fixed issues are re-tested against original failure conditions. The final report lists open items, resolved items, and risk classification for anything deferred.
- Regression coverage logged
- Risk register delivered
- Delivery readiness confirmed
Every engagement ends with a structured handoff document, not just a verbal clearance. The team receives a clear record of what was tested, what passed, and what remains.
What the process
actually produces
Each phase ends with a written output — not a conversation. Clients receive a defect log, a performance profile, and a risk register, all in a format that integrates with standard issue trackers.
Selmurat has been running this process since 2016. The structure has been revised based on recurring failure patterns observed across real XR deployments, not theoretical frameworks.
See the full list of servicesAverage client rating across 196 reviewed projects. Ratings reflect process clarity and defect detection accuracy, not just delivery speed.
Typical number of distinct device configurations validated per engagement, covering both standalone and tethered headsets.
Tracking drift is the defect clients notice last but experience first. We measure it on day one.
Frame pacing issues rarely appear in average FPS. The variance is where the real data lives.
Anchor persistence breaks differently on each platform. A single test pass across three devices is not enough.
A bug report without reproduction steps is just a complaint. Every defect we log can be reproduced in under three minutes.