CNA-VGAP-007: The SDL3 camera provider and file-dialog result path have no test that drives them, and the tray is tested only against a stand-in SDL

CNA snapshot 3b43bd86  ·  Known Issues › Verification gaps  ·  source links pinned to 3b43bd86

Sdl3Camera.cpp and the SDL3 dialog trampoline are exercised by no test beyond capability presence and empty-callback refusal; Sdl3Tray.cpp is now linked against a stand-in SDL seam, but no test creates a real tray icon.

Identifier

CNA-VGAP-007

Category

Verification gap

Subsystem

Platforms

Status

Narrowed (partially fixed; describes only what survives)

Verified against

CNA 3b43bd86 (3b43bd8687ed46523d873f9bec4b32bd8481dcb5)

Evidence basis

Source-verified: read at TARGET, not executed

Tests touching this area

Yes: see Current tests

Affected contract

The SDL3 camera provider and sessions, tray icons and file dialogs (Sdl3CameraProvider, Sdl3Tray, Sdl3Dialogs) behind CNA::Devices::Camera, SystemTray and FileDialog

Expected behaviour

Each platform service that backs a public CNA::Devices class has at least a headless or dummy-driver test of its own contract: permission-state mapping and row compaction for the camera, entry callbacks and icon lifetime for the tray, result delivery (including the failure case) for dialogs.

Actual behaviour at TARGET

No test refers to Sdl3Camera or Sdl3CameraProvider; Sdl3PlatformTests.cpp and PlatformConformanceTests.cpp only check that GetCamera() and GetTray() are non-null exactly when the capability is set. Sdl3SystemServicesTests.cpp checks that the file dialogs refuse an empty callback; nothing reaches ResultTrampoline. Since 93baa9363 (2026-10-22) tray_label_lifetime_test.cpp links the real Sdl3Tray.cpp against a stand-in for SDL's tray functions and fires entry callbacks through it, which covers label and callback storage; it says itself that it is not evidence of a real StatusNotifier host, and the D-Bus harness beside it is a manual tool. No test creates a tray icon through the real SDL, or checks the thread its callbacks run on. CameraTests, SystemTrayTests and FileDialogTests use CannedCameraPlatform, CannedTrayPlatform and CannedDialogPlatform, so they prove the wrappers' forwarding, not SDL3 behaviour.

Source locations

• modules/platform/src/Sdl3/Sdl3Camera.cpp — session state latching, TryAcquireFrame and row compaction
• modules/platform/src/Sdl3/Sdl3Tray.cpp — EntryClickTrampoline, callback storage, IsSupported
• modules/platform/src/Sdl3/Sdl3SystemServices.cpp — Sdl3Dialogs and ResultTrampoline
• modules/platform/tests/CNA/Platform/Sdl3PlatformTests.cpp — service presence only
• modules/platform/tests/CNA/Platform/Sdl3SystemServicesTests.cpp — FileDialogsAreSupportedAndRejectAMissingCallback
• modules/devices-ext/tests/CNA/Devices/CameraTests.cpp — runs against the canned camera platform

Evidence

Checked by searching the TARGET test tree for the SDL3 camera, tray and dialog types and reading the matching tests at 3b43bd86; not executed. The devices-ext internals page states the same for the camera provider.

Focused reproduction

No focused reproduction is known. Nothing has been invented here; the evidence above is what exists.

Current tests

As listed above: presence checks, the empty-callback refusal, and the canned-platform wrapper suites.

Regression test

A camera test against an SDL camera driver usable in CI, where the pinned SDL offers one (not checked here), covering permission states and a compacted RGBA frame; a tray test that creates an icon and fires an entry through SDL on a host with a tray; a dialog test that drives ResultTrampoline's null-list and empty-list cases through a seam, without showing a real dialog.

Blast radius

Evidence only: real SDL3 camera capture, tray menus and dialog result delivery on desktop hosts are unproven by CNA's own suites. The wrappers' logic has tests.

Workaround

No workaround is known.