Skip to content

P3: Automate OBS scene/source smoke tests #103

Description

@iamfatness

Problem

Scene/source regressions have repeatedly reached manual testing. We need automation that proves sources, docks, scenes, looks, and package contents load.

Outcomes

  • Scripted OBS launch validates plugin load, source creation, dock registration, scene template creation, and package layout.
  • Sidecar/obs-websocket smoke tests validate render-plan to OBS actions.
  • CI records artifacts/logs on failure.

Acceptance criteria

  • Smoke test can run locally before release.
  • GitHub Actions build fails on missing plugin/runtime/Qt/SDK dependencies.
  • Test artifacts include OBS logs and CoreVideo diagnostics.

Activity

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

    area:releaseInstaller, packaging, CI/release automationpriority:P3Longer-term scale/commercial polishtype:hardeningReliability, diagnostics, quality, supportability

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions