Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 20 additions & 19 deletions docs/skills/test-authoring/gnome/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,13 +49,13 @@ metadata:
## Stack


| Layer | Component | Install |
|---|---|---|
| BDD runner | behave | pip |
| Session bridge | qecore-headless | pip |
| GUI automation | dogtail (AT-SPI) | pip |
| Wayland coord bridge | gnome-ponytail-daemon | `sudo dnf install gnome-ponytail-daemon` inside VM |
| Shell bridge | `org.gnome.Shell.Eval` | built-in (requires `unsafe_mode=true`) |
| Layer | Component | Install |
| -------------------- | ---------------------- | -------------------------------------------------- |
| BDD runner | behave | pip |
| Session bridge | qecore-headless | pip |
| GUI automation | dogtail (AT-SPI) | pip |
| Wayland coord bridge | gnome-ponytail-daemon | `sudo dnf install gnome-ponytail-daemon` inside VM |
| Shell bridge | `org.gnome.Shell.Eval` | built-in (requires `unsafe_mode=true`) |

## Screen Lock/Unlock D-Bus calls (GNOME 50)

Expand Down Expand Up @@ -91,9 +91,18 @@ test manual session locking via `loginctl lock-session` / `loginctl unlock-sessi
and logind `LockedHint`, which remain fully operational even when automatic idle
lock is disabled.

## GNOME 51 workarounds audit (issue #827)
## GNOME 51 (issue #827)

GNOME 51 (GA 2026-09-16) is Wayland-only and freezes the extension API. Keep every GNOME 50 workaround until a `gnomeos-51` run proves it obsolete — inventory, ground rules and validation procedure in [`references/gnome-51-audit.md`](references/gnome-51-audit.md).
`dakota:testing` and `utah:testing` run GNOME Shell 51.1 (qecore 4.19.3 works).
Each GNOME 50 workaround's GNOME 51 verdict, with probe evidence, is in
[`references/gnome-51-audit.md`](references/gnome-51-audit.md). Still needed on
51: the Files AT-SPI name `org.gnome.Nautilus`, and Ptyxis's `Terminal` title
where Ptyxis ships. The rest are obsolete on 51; keep their GNOME 50 paths while
any tested image runs GNOME 50. Notification dismissal checks that the test
notification is gone, not that no banner shows: Shell holds earlier banners on
screen while the session is idle, as a headless VM always is. Calculator and
Text Editor divergences on plain GNOME OS 51:
[`references/gnome-51-app-divergences.md`](references/gnome-51-app-divergences.md).

## Remote session commands from the runner container

Expand Down Expand Up @@ -474,15 +483,6 @@ helper; key contract points:
Reuse this helper rather than a new `gdbus`-poll loop. See
`docs/skills/ci-ops/ops/references/qecore-headless-restarts-gdm-bus-socket-churn.md`.

## GNOME 51 workarounds audit

`dakota:testing` runs GNOME 51.1; its e2e smoke runs exercise workarounds on
GNOME 51. Keep GNOME 50 workarounds while any tested image still needs them.
See `references/gnome-51-audit.md` for run evidence and per-workaround verdicts.
Calculator display lookup and Text Editor new-document/quit diverged on plain
GNOME OS 51. When the PR validation plan selects VM-covered suites, the check
runs `dakota:testing`; it cannot capture AT-SPI trees for apps that image lacks.

## On-demand references

Load these when you hit the specific topic:
Expand All @@ -491,7 +491,8 @@ Load these when you hit the specific topic:
- [Top-bar interactions and Shell.Eval parsing on GNOME 50+.](references/top-bar.md)
- [MIME, display, and session configuration in containerized tests.](references/display-config.md)
- [Deep dive: Preinstalled Flatpak desktop app launch checks](references/preinstalled-flatpak-desktop-app-launch-checks.md)
- [GNOME 50 → 51 workaround audit, live run evidence, and the Calculator / Text Editor divergences.](references/gnome-51-audit.md)
- [GNOME 50 → 51 workaround audit and its targeted probe evidence.](references/gnome-51-audit.md)
- [Calculator and Text Editor divergences on plain GNOME OS 51.](references/gnome-51-app-divergences.md)

## Overview, clone paint, and helper fault injection (issue #919)

Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
---
name: gnome-51-app-divergences
description: "Calculator display lookup and Text Editor new-document/quit failures found in the plain gnomeos-51 run; documented, not fixed. Not among the twelve audited GNOME 50 workarounds."
metadata:
type: reference
audience: agents
maturity: stable
---
# GNOME 51 app divergences: Calculator and Text Editor

These are **not** among the twelve workarounds above. In the plain `gnomeos-51`
run ([gnome-51-audit.md](gnome-51-audit.md) §Run evidence), Calculator and Text Editor scenarios diverged. In the `dakota:testing`
v1 gate run (same section), both apps were absent and their scenarios skipped; that run
does not show them passing or failing. When the PR validation plan selects
VM-covered suites, the check runs `dakota:testing`; it cannot capture AT-SPI
trees for apps that image does not ship.
The findings below are **documented here, not fixed**.

### Calculator display lookup — broken on 51

- **Failing:** `basic_multiplication` ("display shows 42"),
`subtracting_to_a_negative_result` ("display shows -5").
- **Passing (decoys):** `basic_addition` (3), `basic_division` (3),
`basic_subtraction` (5), `clear_button_resets_display` (0),
`decimal_arithmetic` (3), `calculator_launches`.
- **Root cause:** `click_calculator_button` / `Calculator display shows` in
`tests/smoke/features/steps/gnome_calculator_steps.py` resolve the display via
`_display_candidates()`, which walks the window for nodes with role in
`{text, entry, label, static}` and a non-empty value. On GNOME 51 the display
node is **not** located, so the step falls back to the keypad **buttons**
(7, 8, 9, `×`, `÷`, `−`, `+`, `=`, …). A single positive digit that happens to
equal a button label (`3`, `5`, `0`) matches by accident and passes; `42` and
`-5` match no button and fail. The screenshot
`screenshot_smoke_failed_basic_multiplication.png` shows the calculator with
no display value matching.
- **What the run proves:** the step did not locate the display node on this
`gnomeos-51` image. Capture the app's GNOME 51 AT-SPI tree to identify the
real display node or distinguish it from the keypad buttons.
- **Also failing:** `calculator_closes_cleanly_via_ctrl_q` — `Ctrl+Q` did not
quit (see Text Editor below; shared key-combo path).

### Text Editor new-document / quit — broken on 51

- **Failing:** `text_editor_creates_new_empty_document_buffer` (`Ctrl+N`),
`text_editor_save_dialog_is_open` (`Ctrl+S`), `text_editor_discard_dialog_is_open`
(`Ctrl+Shift+S`), and the Text Editor coredump/quited scenarios.
- **Passing:** `text_editor` `@input` ("Type text") — plain typing works.
- **Root cause:** after `Ctrl+N` the buffer still shows the previous scenario's
content (`"Bluefin smoke testPrevious document content"`) instead of a new
empty buffer. `Ctrl+N` is not creating a new document on GNOME 51. Plain
character entry via uinput works, so the input layer is fine — the failure is
specific to the `Key combo` path (`Ctrl+N`/`Ctrl+S`/`Ctrl+Shift+S`).
- **What the run shows:** the `Key combo` step did not drive the expected
accelerator for Text Editor on this `gnomeos-51` image. A run with `qecore`
debug logging is needed to establish whether the combo is dropped or mis-routed.
Loading
Loading