Testing and Verification

Testing and Verification

This page captures the normal validation flow for Blockiverse VR changes.

Repository Checks

bash -n scripts/ci/forbidden-files.sh scripts/unity/*.sh
scripts/ci/forbidden-files.sh
test -f docs/architecture/branching-and-release.md

GitHub-hosted CI validates repository checks. Unity validation is manual and local unless the project later adopts a CI-compatible Unity license or self-hosted runner.

Unity Validation

Run local Unity validation before moving Unity-impacting work to review or merge:

scripts/unity/run-tests.sh
scripts/unity/build-development-apk.sh /tmp/blockiverse-vr-development.apk

The test script writes NUnit XML results to:

• TestResults/Unity/EditMode.xml
• TestResults/Unity/PlayMode.xml

If Unity batchmode logs stale licensing-client errors such as ResponseCode: 505, reset Unity Hub and licensing processes before retrying.

Manual Quest Validation

Manual Quest validation matters for user-facing or release-facing work. Use Meta Quest 3 and Quest 3S when available, and record exact device, build, and command evidence.

Useful device checks:

hzdb --version
hzdb device list
hzdb log --tag Unity --level I --lines 200
hzdb log --tag Unity --level W --lines 200

Do not commit local logs, screenshots, recordings, traces, APKs, or other generated validation artifacts unless a tracked artifact is explicitly required.

Scenario Coverage

Important validation areas:

• Boot scene launches to a usable menu.
• Creative placement/removal and hotbar selection.
• Survival resource harvest, inventory, crafting, stations, containers, and vitals.
• Save/load, autosave, migration, corrupt-save handling, and recent-save continuation.
• survival_terrain, flat_builder, and void_builder world presets.
• Day/night, weather, lighting, biome vegetation, structures, and loot.
• LAN host/join, late join, reconnect/error handling, and host-authoritative block/inventory/survival sync.
• Meta Horizon avatars or fallback proxies.
• Audio, haptics, VFX, weather ambience, UI cues, and feedback settings.
• Comfort menu, teleport, snap turn, height reset, readable world-space UI, and controller disconnect/reconnect.
• Performance budget and OVR Metrics captures for release candidates.

Store Candidate Validation

Store-candidate checks include VRC, store-copy consistency, privacy/support URLs, screenshots/captures, performance evidence, signed release APK packaging, and manual Quest hardware acceptance.

See Release and Store Readiness.