Skip to content

Run cooked-scene Vulkan smoke tests on a GPU-capable CI runner #885

Open

Description

@JeanPhilippeKernel

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 CTest CookedDesktop smoke 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions