Testing And Verification

Last reviewed: 2026-06-30

Available Verification Surfaces

Surface	What it verifies	Source
MkDocs strict build	Documentation links, nav, markdown buildability.	mkdocs build --strict
Unity batchmode import/compile	Project imports and scripts compile.	Unity command in docs/process/ChangeWorkflow.md
Unity Test Runner	EditMode/PlayMode tests, if assemblies exist.	Unity Test Framework package present
Protocol simulator scene	Unity-style ZeroMQ command/status/heartbeat protocol without full renderer.	Assets/Anuva/Scenes/Anuva_Simulator_Scene.unity
Bot motion tester	Manual preview of generated/loaded bot motion plan.	BotMotionPlanTester, custom inspector
Bot animation sequence tester	Manual preview of bot animation sequence JSON.	BotAnimationSequenceTester
Local renderer scene playback	End-to-end config/media/camera/capture smoke test.	Anuva_DemoSet_Scene / Anuva_TataMotors_Scene
Python fake/real integration	Protocol compatibility with Python Server.	Python repo tests and AnuvaPythonServerCommunication

Commands

mkdocs build --strict

& "C:\Program Files\Unity\Editor\Unity.exe" -batchmode -quit -projectPath "$PWD" -logFile "Logs/UnityBatchmode.log"

& "C:\Program Files\Unity\Editor\Unity.exe" -batchmode -quit -projectPath "$PWD" -runTests -testPlatform EditMode -testResults "TestResults/EditMode.xml" -logFile "Logs/EditModeTests.log"
& "C:\Program Files\Unity\Editor\Unity.exe" -batchmode -quit -projectPath "$PWD" -runTests -testPlatform PlayMode -testResults "TestResults/PlayMode.xml" -logFile "Logs/PlayModeTests.log"

Current Test Coverage

No first-party NUnit/EditMode/PlayMode test assembly was discovered under Assets/Anuva. Files with Tester in their names are manual/editor/play-mode helper components, not automated test suites.

Python-side protocol tests exist in anuva-python-server, including fake Unity ZeroMQ integration tests. Unity-side compliance tests against the Python client are Unknown / not confirmed in this repo.

Manual Render Verification Checklist

Record these when validating a render:

• Unity version: 6000.3.14f1
• Scene path
• Config source URL/path
• Media server/source availability
• Capture output path
• Resolution/frame rate
• Realtime vs offline capture
• Whether Python communication was enabled
• Whether final MP4 exists and has non-zero size
• Unity log warnings/errors
• Python render.* messages, if running remote mode