Repository navigation
Open
Labels
DevOpsP2High priority — next sprintHigh priority — next sprintenhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededvulkan-api
Description
Context and problem
PR #879 adds real cooked-scene desktop smoke tests under the opt-in ZENGINE_ENABLE_COOKED_DESKTOP_TESTS CMake option. The existing scene-evidence-tests CI job exercises the Python evidence tools, not a real Vulkan process. A successful evidence job therefore does not prove that the standalone cooked scene actually rendered in CI.
Work
- Design and add a separate, appropriately named GPU-capable CI job or documented scheduled/manual runner for the real fresh-process test. Keep evidence-tool unit tests separate from rendered tests.
- Build the actual host and
SceneCookProcess, prepare a fixture using the production cooker and codecs, and execute the CTestCookedDesktopsmoke path with source-access audit and Vulkan validation. Use a supported desktop session, working Vulkan device/driver, and record the environment. - Include a normal first-frame load and a representative failure/cancellation or replacement path. Ensure a missing GPU, missing validation layer, skipped test, or absent test registration is reported as unavailable/failure according to the job's declared policy, not a pass.
- Document commands, prerequisites, how to run locally, and what the test establishes. Keep headless CPU-only jobs usable; do not substitute a mock for the rendered check or claim coverage on platforms without actual rendered evidence.
Acceptance and verification
- CI or an approved reproducible GPU runner runs the real executable against a freshly cooked fixture, checks successful frame submission and zero source-registry/import audit counters, and rejects validation errors.
- Deliberately break the fixture or runtime command to demonstrate that the job detects failure; verify that an unavailable GPU cannot silently produce a green rendered result.
- Identify the supported OS/driver/device scope and document limitations. Link the job and results to [Feature] M2: source-independent cooked scene loading and complete first-frame rendering #873 and feat(scene): reconstruct cooked scenes for standalone runtime #879. The separate editor-free binary in feat(runtime): add editor-free scene executable #883 can reuse this infrastructure after it lands.
Metadata
Metadata
Assignees
Labels
DevOpsP2High priority — next sprintHigh priority — next sprintenhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededvulkan-api
Activity