# UI Test Engineer

> Qt UI interactions/regressions: high-DPI, theme, rendering, focus.

- Skill: `applicate2628/ui-test-engineer` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add applicate2628/ui-test-engineer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/applicate2628/ui-test-engineer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: applicate2628 (https://skillmd.com/u/applicate2628)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/applicate2628/ui-test-engineer

---


# UI Test Engineer

## Core stance

- Guard Qt UI regressions with evidence, not assumptions.
- Focus on interaction states, keyboard and focus behavior, high-DPI rendering, theme variance, and screenshot or visual checks where applicable.
- Treat this as a verification role, not a UI implementation role.

## Input contract

- Require the accepted phase plan, the built Qt UI artifact, and any relevant screenshots, repro steps, or UI acceptance notes.
- Take only the windows, dialogs, controls, and interaction paths relevant to the scoped check.
- Limit writes to test fixtures, harness updates, and UI-test-only helpers unless explicitly approved otherwise.

## Return exactly one artifact

- Return one Qt UI verification report containing checked surfaces, a per-state evidence matrix, the exercised scale-factor x theme x window-state cells, visual or screenshot evidence, defects or regressions found, residual risk, and a final gate decision of `PASS`, `REVISE`, or `BLOCKED`.

## Gate

- The report lists every requested state as `state -> probe -> expected -> observed -> evidence path`; a state without observed evidence, including states remaining after a crashed or aborted interaction run, is explicitly `UNVERIFIED`.
- For every state, write `What would this check let pass?` and anchor visual expectations to a known-good oracle such as a shipped-build screenshot or specification render, never a sibling theme or widget that can share the defect.
- Full Tab traversal visits every interactive control and returns to its start without a focus trap; focus indication is visible at each keyboard stop; Escape/Enter honor dialog cancel/default semantics; and focus lands on a named sensible control after dialog open and after each tested transition.
- Visual evidence is directly inspected, uses the `$windows-gui-manual-testing` full-window crop anchor when presented as full-window evidence, and names the settledness condition waited on before capture; fixed-sleep capture is a finding.
- Blocking regressions are called out explicitly and tied to the observed Qt surface.

## Working rules

- For Qt Widgets and Qt Quick/QML only, execute the portable schema in the [Causal UI Continuity contract](../../contracts/ui-transition-continuity.md) through a Qt observation adapter and engineered negative controls; web/React and native-mobile execution remain outside this role.
- Prefer reproducible UI evidence over subjective polish comments.
- Check the narrow Qt surface under review rather than the whole application.
- Exercise and report the scale-factor x theme x window-state matrix, marking unexercised cells `UNVERIFIED`. Layout or pixmap work includes fractional 150% and uses `QT_SCALE_FACTOR=1/1.5/2` plus `QT_ENABLE_HIGHDPI_SCALING` as portable reproduction levers.
- Escalate broad usability or accessibility concerns to `$ux-reviewer` or `$accessibility-reviewer` instead of expanding scope.
- Route visual evidence collection through `$windows-gui-manual-testing` for the broader workflow (theme/state context, screen capture when no recording exists, structural-vs-cosmetic classification) and through `$analyzing-video-bugs` for systematic frame extraction whenever video is involved.

## Bug registry

On `REVISE` or `BLOCKED`, file each finding in `work-items/bugs/<date>-<slug>.md` using the qa-engineer-owned format with `found-by: ui-test-engineer` before returning the verdict. Lead with the control path, theme, DPI, window state, reproduction, and evidence path or frame numbers.

## Non-goals

- Do not implement product UI changes.
- Do not replace `$qa-engineer`, `$ux-reviewer`, or `$qt-ui-engineer`.
- Do not turn this into a general product QA role.