Classroom_Desktop/docs/testing.md

Classroom test checklist

Run against the exact artifact published to canary, on the real endpoint, before promoting to stable with ./update_stable.sh.

Boot

• Cold boot reaches the classroom shell with no terminal or window junk
• Reboot does the same
• Wallpaper appears
• Dock appears, centred
• Clock appears, bottom right

The television switched on after a night-time reboot

This is how Tiny Pebbles lost its wallpaper after the 0.2.2 upgrade, and the lab cannot do it: KWin will not start a session with no screen, and the lab cannot plug one in. The lab proves the same code path through a new activity (tools/lab/wallpaper-check); only a real television proves that switching it on takes that path. See ui-scale.md. Do it once, on a desktop whose television is switched off at the set, not the remote:

1. Television off at the set. sudo reboot, and wait five minutes.
2. Television on. The classroom's landscape is on the screen, not Plasma's purple wallpaper. The panel is the room's own.
3. From the maintenance terminal (Meta+Ctrl+Alt+Shift+K), classroom-desktop-wallpaper --check. Note what it says. If it names a desktop that "had no wallpaper configured", the television really did arrive after the shell, and the screen in step 2 is the fix working
4. systemctl --user restart plasma-plasmashell.service: the panel blinks and comes back, open windows stay, the wallpaper is unchanged
5. classroom-desktop-wallpaper --check now says "the classroom wallpaper already"
6. Reboot with the television on: the same picture and the same panel

Tiny Pebbles can confirm the cause before it takes the release, because the update reboots it and a login rebuilds the file. If its panel was built with no screen, the panel is [Containments][1] next to the desktop's 10:

grep -A6 '^\[Containments\]\[[0-9]*\]$' \
    ~/.config/plasma-org.kde.plasma.desktop-appletsrc | grep -E '^\[|^plugin='

Provisioning

• journalctl -u ekklesia-classroom-provision shows a clean run
• Google Chrome is installed on a machine that never had it
• A second boot does not reinstall anything
• A machine with no network still boots to a working shell, and provisioning succeeds at a later boot once it is online

Networking

• nmtui is installed and NetworkManager.service is enabled
• An Ethernet interface declared in /etc/network/interfaces remains managed by ifupdown and keeps its existing address
• sudo nmtui can save and activate a Wi-Fi connection
• The saved Wi-Fi connection reconnects after reboot
• A machine with no Wi-Fi adapter reaches the classroom normally without an online-wait delay or NetworkManager failure
• Ethernet-only operation is unchanged

Printing

• cups.service is enabled and lpstat -r reports that the scheduler runs
• lpinfo -m contains the generic color PCL 6/PCL XL driver documented in printing.md
• sudo classroom-printer-setup creates only Elmer, enables it, and makes it the system default
• Provisioning creates Elmer automatically at socket://10.10.0.155:9100 with description Elmer
• lpoptions -p Elmer -l shows *Normal for PrintoutMode and *Color for ColorModel
• An upgrade removes the old Classroom_Color queue
• Repeating provisioning reports Elmer already configured and does not rewrite the queue
• Chrome opens the system print dialog and shows only Elmer
• lpstat -e prints only Elmer; neither the Brother label printer nor a discovered duplicate Ricoh appears
• avahi-daemon.service and avahi-daemon.socket are masked
• The CUPS test page prints in color on the Ricoh MP C3502
• With the Ricoh powered off, the classroom still boots normally and a job simply remains queued

Secondary Chrome windows

• The first Chrome top-level remains maximised, tiled and borderless
• A second google-chrome top-level floats instead of splitting the main browser
• It is centred at roughly three quarters of the logical display
• Its red Close button is visible and mouse-accessible
• Close removes only the secondary and reveals the untouched main browser
• Changing either page title does not change the main/secondary roles
• A third Chrome top-level also floats and Close targets the newest one
• Chrome minimise/restore and the dock Browser button still behave normally

UI scale

UI_SCALE sets sway's output scale, so it scales the whole session. Change it, then sudo systemctl restart getty@tty1.

• UI_SCALE=1.0 is identical to a session with no scaling
• swaymsg -t get_outputs shows the mode still 1920x1080 at every scale, with only the logical size changing
• At 1.25 and 1.5, Chrome grows: tabs, omnibox, toolbar icons, menus and page content
• Chrome's buttons are still easy to hit with the mouse
• Dock, clock, notifications and the DVD bar grow by the same amount — once, not twice
• Dock icons stay crisp at 1.25 and 1.5 on a normal-density monitor, not just from across the room: compare an icon against the clock text beside it
• DVD control bar icons are crisp at the same scales
• UI_SCALE=0.8 shrinks everything together
• A nonsense value (UI_SCALE=banana) still gives a working shell
• An extreme value (UI_SCALE=9) is clamped, not obeyed
• journalctl or the sway log shows classroom-scale: session scale N

Reserved bottom shell (regression)

The bottom strip is one full-width layer-shell surface with a 76px exclusive zone. Dock and clock live inside it. Do not split them back into separate layer-shell windows.

• A maximised Chrome window stops above the bottom strip
• The clock does not float over Chrome
• Dock stays centred, clock stays bottom right
• Wallpaper shows through the unused parts of the strip
• Every dock button still responds to clicks
• A fullscreen application covers the whole display, dock included

Browser

• First Browser click launches Chrome
• Chrome opens on Wonder Ink (https://app.wonderink.org/)
• Clicking Browser while Chrome is focused minimises it
• Clicking Browser again restores it maximised, not floating or draggable
• Clicking Browser while Chrome is running but unfocused focuses it
• Super+M minimises the focused window
• Super+Shift+M restores the most recently minimised window
• Normal navigation to any other site works
• The Home button returns to Wonder Ink
• Fullscreen YouTube video uses the whole display
• Leaving fullscreen restores the correct geometry above the dock
• The main Chrome window has no sway title bar — it starts at Chrome's own tab strip, and Chrome's tabs and address bar are still there
• Chrome still maximises and minimises as before
• After a reboot, no "Restore pages? Chrome didn't shut down correctly" bubble
• Chrome does not offer to save passwords
• Chrome shows no way to sign into the browser itself
• No "Add profile" and no Guest entry in the profile menu
• No profile picker at startup
• Wonder Ink signs in normally during a session
• After closing Chrome fully and reopening, Wonder Ink is signed out (see browser.md — this is the unverified one)
• YouTube is still signed into the church account after that
• chrome://policy lists PasswordManagerEnabled as an applied managed policy
• Website logins still persist across a reboot
• Clicking Browser when Chrome is closed shows a throbber on the dock button until the window appears
• Clicking Browser when Chrome is already open feels immediate, with no throbber
• The pointer shows a busy cursor while it is over the dock
• No first-run, default-browser or sign-in nag appears
• chrome://policy lists the Ekklesia policies as applied, with no "unknown policy" entries
• Chrome does not start by itself at boot
• After a reboot, cookies and site logins are still there
• After an OTA update, cookies and site logins are still there

Known limitation: Chrome's own minimise button in its title bar does nothing. Sway ignores the Wayland minimise request and gives no event to hook. Minimising is the dock's Browser button or Super+M.

Notifications

• classroom-notify-test renders with the classroom styling: dark translucent, rounded, white text, top right
• classroom-notify-test --critical "Parent Call" "Room 3 needs a parent." renders in the critical style and does not time out
• Notifications appear over a fullscreen video

Over SSH from an administrator account, run it with sudo:

sudo classroom-notify-test --dry-run   # show the session it resolved
sudo classroom-notify-test             # send into the classroom desktop

The classroom desktop belongs to the classroom user, and mako sits on that user's D-Bus session. A plain notify-send from an SSH session lands in the administrator's own session, where nothing owns org.freedesktop.Notifications, so D-Bus tries to start a second mako with no display and the call times out with NoReply. The script finds the running sway process for the classroom user and delivers into its session instead. It never starts mako.

• sudo classroom-notify-test from an SSH session displays on the classroom screen
• sudo classroom-notify-test --dry-run reports the resolved XDG_RUNTIME_DIR, bus address and Wayland display
• Running it as an unprivileged admin account explains it needs sudo
• tests/test-classroom-notify-test.sh passes (also run by the build)

Audio

The room prefers the television. AUDIO_OUTPUT in device.conf decides: auto (prefer a connected HDMI or DisplayPort set, fall back to the jack), hdmi, or analog. A machine with no digital output at all — a laptop, when one arrives — is correct on auto without any change here.

Two test suites cover this, and both run in the build:

• tests/test-classroom-audio.sh — the decision itself, against the shapes real pactl emits
• tests/test-classroom-audio-daemon.sh — the real daemon driven through every situation a room gets into, against a pactl that answers the way PipeWire does

On a machine:

• classroom-audio show lists the outputs, what it chose, the profile it would set and whether it is settled
• journalctl --user -u ekklesia-classroom-audio shows one output is ... line per real change and nothing in between
• Leaving the room alone for an hour adds no further lines and no measurable CPU time

The television switched on after the computer

This is the scenario that silenced River Kids on 0.2.2 and the one no lab can produce: ALSA reports a television through the HDMI port's availability, and no loopback or dummy sound driver has such a port. The suites above play it through a mock, and the mock is faithful to the real server as far as it was measured — but a mock cannot prove the real ALSA jack change arrives. Do not take a passing build as evidence that this works. It has to be done at a machine, once, per release:

1. Switch the television off at the set, not the remote.
2. Reboot the computer and let it reach the classroom desktop.
3. Leave it at least two minutes, so any startup settling is over.
4. journalctl --user -u ekklesia-classroom-audio — expect one output is ... line. In a room with nothing in the analog jack it names the HDMI port even now, which is right: there is nowhere better for the sound to go, and the set is then already correct when it comes on.
5. Open Wonder Ink and Chrome and start something playing.
6. Switch the television on.
7. Sound should arrive within about a minute, in both applications, without closing or reopening either one.
8. wpctl status should show the HDMI sink as default, and classroom-audio show should say settled=True.
9. Switch the television off and on again. Sound should come back.
10. Check the volume is where the teacher left it, and that an output muted on purpose is still muted.

If step 7 fails, the jack change is not reaching PipeWire at all; capture pactl subscribe and classroom-audio show with the set off and then on, which is what distinguishes that from a policy fault.

Device features

Every optional application is its own setting in device.conf, and DEVICE_TYPE decides none of them. A laptop can take children's church and a tower can be a Bible study.

DEVICE_TYPE=desktop|laptop        what the hardware IS
WONDERINK_ENABLED=true|false
DVD_ENABLED=true|false            a drive is still required as well
PARENT_CALL_ENABLED=true|false
NETWORK_PREFERENCE=wired|wifi
DISPLAY_MODE=all|external-only

All default to the classroom's existing behaviour, so an upgrade changes nothing until somebody edits the file. classroom-desktop-layout writes the answers into the packaged layout; the bar is rebuilt from it at the next login.

• tests/test-classroom-desktop-layout.sh passes (also run by the build)
• After changing a setting, classroom-desktop-layout then a logout/login shows the new bar
• A disabled application leaves no gap: the remaining launchers close up
• The launcher order is the same on two machines with the same features enabled
• The order survives launching and closing applications, logout/login and a reboot — run tools/lab/order-check against a live session, which opens real windows and reads the bar off the screen
• Right-clicking a launcher offers no Pin or Unpin

Two things the bar cannot do at once

Stock Plasma 6.3 ties them together, and this is the trade the classroom makes. Both halves are measured, not inferred:

main.qml:153  hideActivatedLaunchers: tasks.iconsOnly || ...
main.qml:155  launchInPlace: tasks.iconsOnly && sortingStrategy === 1
MouseHandler.qml:74  accepts a reordering drop only when
                     sortMode === SortManual

For an icons-only bar the launcher is ALWAYS hidden once its application starts. Only sortingStrategy = 1 puts the running window back in the launcher's place — and 1 is also the only value at which a drag can reorder anything.

• sortingStrategy = 0 — no dragging, but the browser jumps behind the disc player when it opens. That was 0.2.4, and it is the bug.
• sortingStrategy = 1 — the order holds through every open and close, and a teacher who knows to drag can rearrange the bar within a session. This is what ships.

There is no third value and no Kiosk key that separates them. classroom-desktop-reset rebuilds the bar from the package at every login, so a drag never outlives the session.

• KNOWN: a drag can still rearrange the bar until the next login
• After logging out and back in, the packaged order is back

The configuration escape (unresolved)

Right-clicking a launcher offers Configure Icons-Only Task Manager…, and that dialog opens and reaches the sorting setting. Measured on the lab session with the desktop locked: plasma/plasmashell/unlockedDesktop reads false, evaluateScript answers "Widgets are locked", Pin and Unpin are correctly hidden — and Configure is not gated by any of it. There is no allow_configure_when_locked key in Plasma 6.3; it was searched for in the shipped libraries and does not exist.

Closing it means overriding stock ContextMenu.qml, which is a fork of a file that changes between Plasma releases. Not done.

• KNOWN: a teacher who opens that dialog can change the sorting, and the next login puts it back
• The bar is right at 1080p/100% and 4K/200%

The Bible study laptop

A laptop installed as a fixed appliance: AC power, battery out, lid shut, one television on HDMI, Wi-Fi.

DEVICE_TYPE=laptop
DISPLAY_MODE=external-only
NETWORK_PREFERENCE=wifi
WONDERINK_ENABLED=false
PARENT_CALL_ENABLED=false
DVD_ENABLED=false

Nothing about DEVICE_TYPE=laptop turns those applications off; they are off because those lines say so.

Physical verification — the Wi-Fi hand-over

No lab can do this one: it needs the laptop's radio. Over SSH, watching, with a way back into the room if it goes wrong:

1. classroom-wifi --check — expect it to name the interface and say ifupdown owns it. Changes nothing.
2. classroom-wifi --adopt --dry-run — expect the three "would" lines. Changes nothing. /etc/network/interfaces must still be identical.
3. classroom-wifi --adopt. It prints each step. Expect it to end with "is NetworkManager's now, and the room is online". If it fails it puts ifupdown back by itself and says so; the machine should still be reachable. classroom-wifi --rollback undoes it later.
4. nmcli device status — the Wi-Fi device must no longer say unmanaged.
5. nmcli networking connectivity — must say full, not none.
6. nmcli device wifi list — must now list networks.
7. Log out and back in. The panel must show the Wi-Fi connection.
8. Reboot. It must reconnect on its own, with nobody typing a password.
9. As the classroom account, confirm the password is still unreachable:
   • nmcli -s -g 802-11-wireless-security.psk connection show <name> must be empty
   • the applet's Show Network's QR Code must not produce one
   • /etc/NetworkManager/system-connections/*.nmconnection must be unreadable
10. As tech, confirm maintenance still works: sudo nmcli -s ... returns the key.

Physical verification — a real lid and a real television

The lab has no lid and no HDMI hotplug, so none of this is proven by a passing build. Do it once at the machine:

1. With the lid open and the television on, check classroom-display-mode reports the panel switched off and the television on, and that only the television is lit.
2. Close the lid. The machine must keep running: the television stays on, audio keeps playing, SSH stays up. systemctl is-system-running still answers, and loginctl shows the session active.
3. Leave it closed for ten minutes. It must not suspend, hibernate, log out or lock. journalctl -b | grep -i -E "suspend|hibernate|lid" should show nothing acting.
4. With the lid still closed, switch the television off and on again. The picture must come back. Known limitation of 0.2.4: the display mode is applied at login, not continuously, so if KWin re-enables the internal panel on that power cycle it stays enabled until the next login. Check whether it does, and report it — that decides whether the follow-up needs an event-driven applier like the audio policy's.
5. Unplug and replug HDMI, lid closed. Same check.
6. Reboot with the lid closed and the television on. It must come back to the classroom desktop on the television.
7. Confirm Wi-Fi reconnects on its own, with nobody typing a password.
8. Confirm the HDMI audio policy still works (see Audio, above).

Messaging

• With MQTT_ENABLED=false, journalctl -u ekklesia-classroom-mqtt shows one line and the service is inactive — and the room is completely normal
• With a broker configured, the service connects and mosquitto_sub -t 'classroom/status/#' -v shows the room online
• A published notification appears on the classroom screen in the classroom styling
• urgency: critical renders in the critical style
• Killing the broker leaves the room entirely usable
• The service reconnects on its own when the broker returns
• Rebooting with the broker down boots normally to the dock
• A retained notification left on the broker does not appear at boot

DVD

With DVD_ENABLED=false:

• No DVD button in the dock

With DVD_ENABLED=true:

• Drive unplugged: button present, icon held back, friendly notification on click
• Drive present, no disc: friendly notification on click, nothing crashes
• Inserting a disc produces one DVD Ready notification
• The DVD icon comes up to full strength while a disc is in
• Nothing plays until the button is pressed
• Clicking plays the disc
• Menus work
• Audio works
• Chapter navigation works
• Fullscreen works
• Super+M minimises the player, the DVD button restores it
• Closing the player works
• Ejecting is detected, the icon goes back
• Reinserting is detected again
• Commercial CSS disc plays without anyone having run codec setup by hand

Sanctuary LIVE capability

With LIVE_ENABLED=false:

• No LIVE button or spacing hole appears in the dock
• No live-specific service or process starts

With LIVE_ENABLED=true:

• LIVE appears after DVD when DVD is enabled, and after Browser otherwise
• Clicking it shows the existing placeholder notification
• No live playback is attempted

DVD mode

• Pressing DVD covers the whole display immediately, dock and clock included — no wallpaper visible anywhere, at any point
• A spinner and "Loading DVD…" show while the disc spins up
• No partial VLC window is ever visible against the wallpaper
• The loading surface stays up until the disc menu is actually showing — VLC's tiled black startup window is never visible
• Video or the disc menu replaces the loading surface when ready
• A disc that never opens still gives the desktop back (20s)
• No VLC chrome anywhere: no menu bar, no fullscreen controller, no cone, no sway title bar
• Wallpaper is never visible around VLC
• Moving the mouse to the bottom slides the classroom bar up
• It hides again shortly after the mouse leaves it
• While hidden, clicking a disc menu item near the bottom still reaches the menu
• Play/pause toggles and the icon follows the actual state
• Previous and next chapter work
• The menu button returns to the disc menu
• Space pauses; arrow keys and Enter navigate the disc menu
• Arrow keys do not change volume, and no key reaches crop, aspect ratio, subtitles, audio tracks or deinterlacing
• Esc leaves DVD mode cleanly, with no black window left behind
• Close leaves DVD mode cleanly
• Eject leaves DVD mode and opens the tray
• Killing VLC by hand also returns to the classroom desktop
• Pressing DVD twice quickly does not start two sessions
• The bar is sized by UI_SCALE like the dock

OTA

• ./update_canary.sh publishes package first, manifest last
• The endpoint on the canary channel picks the update up
• SHA-256 verification passes
• Install succeeds; systemctl list-timers ekklesia-classroom-update.timer shows the next check at about 03:00 tomorrow
• (0.2.6.5) Switched on in the morning after a night off, with an update waiting: it installs, journalctl -u ekklesia-classroom-reboot-when-idle says it is waiting, and it does not restart while you use it
• Play a video with sound and leave the mouse alone for 40 minutes: no restart while it plays; half an hour after it stops, it restarts
• Left untouched with nothing playing, it restarts about 30 minutes after the update, and comes back on the new version
• Everything above still works after the update
• Upgrade from 0.1.36 preserves every existing device.conf value
• LIVE_ENABLED=false is appended exactly once on upgrade and remains single after reinstall
• tools/validate-trixie-release.sh passes against the 0.1.37 package and the 0.1.36 package

Presentations — 0.2.6, the prayer-room laptop

Everything here needs the real television, the real keyboard and the pastor's own session files. The automated tests and the Plasma lab cover the logic and the windows; none of them can tell you that Session 7's text is the right size from the back of the room.

Enable it first, and reboot:

sudo sed -i 's/^PRESENTATIONS_ENABLED=.*/PRESENTATIONS_ENABLED=true/' \
    /etc/ekklesia-classroom/device.conf
sudo reboot

Download

• The bar has a Presentations button, after the Browser
• Wonder Ink and Parent Call are still absent from this laptop
• Download tonight's session in ordinary Chrome
• It does not appear in the library while it is still downloading
• It appears by itself within a few seconds of the download finishing
• The title is readable — not a hash, not a long filename
• The completed original moved out of Downloads into the managed library; there is no duplicate
• Download the PDF and the PPTX of the same session: two cards, the second titled (2), neither overwriting the other

Quick Look

• Quick Look opens on the currently selected cover slide
• Next and Previous move through every slide
• The text and layout are right — check a slide with a Bible verse
• Go to the session-number slide, usually slide 2
• Use as cover changes the card and shows Current cover
• Back to Presentations returns without presenting
• Close the library, open it again: the chosen picture is still there
• Reboot, open it again: still there
• classroom-presentation-import --status shows presented never
• At 1920×1080 and 1366×768, scale 1.0 and the larger supported scale, the title, slide navigation, cover action, Back and Present all remain above the panel without manually resizing

That last line is the one that matters. Quick Look, browsing every slide and changing the picture must not have counted as a presentation.

Present

• Present from the card fills the external television
• No panel, title bar, border, desktop or other application is visible
• It starts at slide 1, not at the slide chosen for the picture
• Present from inside Quick Look does the same
• Space, the arrow keys and Page Up/Page Down all move slides
• The presentation remote's forward and back buttons work
• Fonts and layout are right on the television, from the back
• Esc returns to the library — not the Impress editor, not a terminal, not a blank screen
• Going past the last slide does the same
• --status now shows a presentation time and a count
• Present it again: the count rises and the expiry moves out 30 days
• Unplug the network and present again: it still works

The awkward ones

• A PDF and a PPTX of the same session look the same on screen
• A deliberately broken file gives a short message and only Remove — no editor, no terminal
• A long session (40+ slides) opens without the library freezing
• Download a Wonder Ink worksheet: it does not appear in the library

Remove

Use a test copy. Not tomorrow's session.

• Remove asks first
• The card goes, and its slides and pictures go with it
• Its managed original goes too; unrelated downloads and another similarly named presentation remain
• It does not come back on the next scan or after a reboot

Help is temporarily hidden

• No Help launcher is visible on the teacher-facing bar
• The manual sources, generated HTML/PDF, launcher and feature-aware build pipeline remain installed for the later documentation correction pass
• Presentations and Wonder Ink title bars show only Close, with no double-chevron keep-above control

Wi-Fi — look, do not touch

The laptop's Wi-Fi is already working through NetworkManager and its ifupdown stanza is already gone. Do not run --adopt on it.

• classroom-wifi --check says there is no wireless interface under ifupdown's control
• classroom-wifi --adopt says "nothing to adopt" and changes nothing
• nmcli -g 802-11-wireless.hidden connection show "ROGC Classroom" still reports yes
• The laptop still reconnects after a reboot

Wonder Ink — 0.2.6.1 to 0.2.6.4, before any goes to stable

Everything below was done in the lab except what a lab cannot do: paper, a classroom's own graphics, a real keyboard, its network and its screen. Those are these checks. Stable stays on 0.2.2 until they pass.

Before starting, on each machine: dpkg-query -W ekklesia-classroom must say 0.2.6.4, which carries everything 0.2.6.1 to 0.2.6.3 did. The desktops only get it once stable is moved, so on a desktop install it by hand for the test:

curl -fsSL -o c.deb https://updates.riverofglorymn.org/canary/latest.deb
sha256sum c.deb     # must match .../canary/manifest.json
sudo apt-get install -y ./c.deb && sudo reboot

This does not move the machine to canary (see provisioning.md): its next automatic update follows stable again, which is still 0.2.2 — so after testing, either promote or reinstall 0.2.2 the same way.

Little Waders — printing through Elmer

• Open Wonder Ink, sign in, open a lesson with a worksheet
• Click the worksheet; it opens as a tab named after the file, with a document icon
• Ctrl+P (or right-click → Print page…): the preview shows the worksheet's own pages, page count right, ‹ › turn them
• Printer shows Elmer, preselected
• Print → a notification "Sent to the printer — … — Elmer", Wonder Ink stays open on the lesson
• The worksheet comes out of Elmer, every page, right size, in colour
• Pages 2, Copies 2, Black and white → the preview turns grey, and exactly two grey copies of page 2 come out
• Print a normal lesson page the same way; it comes out, Letter
• Open the preview and press Cancel → nothing prints
• Print three times in a row → three printouts, no crash
• lpstat -W completed -o shows each job; journalctl --user -b | grep "printed '" shows Wonder Ink's line for each

Pictures (0.2.6.2)

• Open a colouring page that is a picture on its own (a PNG or JPEG tab, not a PDF) and press Print: the preview shows it on white — no black bars — with a Picture section under Color
• Size 50%, the top-left square: the preview shows it there, the rest of the page blank. Print it: the paper matches the preview
• Paper Sideways, then Upright: the preview turns; print one
• Fill the whole page: the preview shows the edges cut off; Cancel prints nothing
• A worksheet PDF still prints with no Picture section
• The print dialog says Color, not Colour

Black and white, and Print image (0.2.6.3)

The lab measured all of this on the files CUPS kept, and under the real Plasma session for the clipboard. What it cannot show is Wonder Ink's own site (no account), real paper, and a classroom's own keyboard and mouse.

• A lesson page with colour on it: Ctrl+P, then Black and white → the preview says Preparing black and white… for a moment, then the page is grey. Color → colour again. Back and forth three times: it is instant after the first, and stays on the same page
• Print it in black and white: the paper matches the grey preview
• The same with a worksheet PDF (a few pages), in black and white
• Choose Black and white, then Color, then Print → it comes out in colour
• In a lesson, right-click on a picture (not the words): the menu has Print image… and Print page…. Right-click on the words: only Print page…
• Print image… on a picture you cannot open in a tab by itself: the preview shows that picture on white, with the Picture section — not the lesson page
• Size 50%, the top-left square, Black and white → the preview shows a grey picture in the top-left quarter. Print it: the paper matches the preview
• Print image on a picture with a transparent background (a clipart animal, a logo) → white around it on paper, not black
• Print image, then Cancel → nothing prints
• Copy some words in the browser, then use Print image in Wonder Ink, then paste in the browser → the words paste, not the picture
• If any picture says could not be taken from the page: note which lesson and which picture. Right-click the same picture again once the page has finished loading. If it still says so, that picture is drawn in a way the engine does not treat as a picture — tell us where it is
• If right-clicking an obvious picture offers only Print page, the site draws it as a background. Note which lesson — it is the one case Print image cannot reach

Size and zoom

• A lesson in Wonder Ink is the same size as the same page in the browser on that machine (it was smaller in 0.2.2)
• Ctrl and + (the real keyboard), Ctrl and −, Ctrl and 0 change it; a "Lesson size" badge appears
• Open a second tab: it is the same size; the − 100% + and Print buttons are at the top right
• Close Wonder Ink and open it again: the size is remembered
• A worksheet tab's own − / + (in the PDF toolbar) zoom it
• A lesson video still goes fullscreen and comes back with the tabs

Loading, and the machine's graphics

From the maintenance terminal (Meta+Ctrl+Alt+Shift+K), in the session:

classroom-wonderink --diagnose

• Note the GPU line. A driver's name is right. "none … drawing in software" means QtWebEngine has no GPU on this machine — compare chrome://gpu in the browser; if Chrome has one, that is the cause of slow lessons and is the next thing to fix
• Note the sign-in time (the lab: about 2.9 s wired). Much slower here with a driver named above points at the network
• free -m: Wonder Ink needs about 610 MB plus 115 MB per extra tab

Temporary workspace restore (0.2.6.4) — Little Waders

Use a Viewer account. An Admin sees lessons in WonderInk's editor, where a click on a link shows its Edit/Unlink bubble — WonderInk's design, not Wonder Ink's; Ctrl+click opens it. See wonder-ink.md, Links in a lesson.

1. Sign in to the real WonderInk site
2. Open three lesson/resource tabs: the lesson, and two of its links — for example Saul Welcome Question Slide and a video or worksheet
3. Click the middle tab
4. Close Wonder Ink (the × at the top right)
5. Open it again straight away from the panel
6. The WonderInk tab asks you to sign in — sign in normally (your password is never kept, so it always will)
7. The recent tabs are back: the slide and the other resource
8. In the same order as before
9. With the middle tab in front
10. Open a worksheet from a lesson, then close and reopen Wonder Ink: the worksheet tab comes back, named after the file
11. Print from a restored tab (the slide or the worksheet) through Elmer: the paper matches the preview
12. Links still open with one click in a new tab, as before (Viewer)
13. With the tabs open, reboot the computer; within two hours of using Wonder Ink, open it again
14. The recent tabs are back (after signing in on the WonderInk tab)
15. Expiry, without waiting two hours. Close Wonder Ink. Open the maintenance terminal (Meta+Ctrl+Alt+Shift+K) and run CLASSROOM_WONDERINK_TEST_WORKSPACE_SECONDS=120 classroom-wonderink. This is test-only: it lasts as long as that one Wonder Ink, can only shorten the time, and nothing in the classroom sets it
16. Open a couple of tabs in it, click in one, then touch nothing for three minutes and close it
17. Open Wonder Ink from the panel: it starts fresh, one tab on the WonderInk start page, none of the old tabs

Presentations under memory pressure (0.2.6.2, the laptop)

• Download a large, photo-heavy deck with Wonder Ink and Chrome open: it either becomes ready, or its card says This needed more memory … choose Try again — never Getting this ready… for more than a few minutes
• Close the other programs and choose Try again: it becomes ready
• systemctl --user status ekklesia-classroom-presentations is active, and journalctl --user -u ekklesia-classroom-presentations shows no restart loop

Settings the teacher must not reach (0.2.6.2)

• When any notification shows the sliders (Configure) button, clicking it opens only The module … is disabled; its Help button does nothing
• Right-click the clock: no Configure Digital Clock…; Adjust Date and Time… opens an empty System Settings
• Right-click the volume: no Configure Audio Devices…
• The maintenance chord (Meta+Ctrl+Alt+Shift+K) still opens a terminal, and systemsettings started from it is complete

After a reboot, and the other rooms

• Reboot Little Waders: it comes up as the classroom, Wonder Ink opens
• On one other desktop, 0.2.6.1 installed: the browser, the DVD player where there is a drive, Parent Call where enabled, sound through the television, the panel order — all as on 0.2.2
• Presentations is not on the panel of any desktop (grep PRESENTATIONS_ENABLED /etc/ekklesia-classroom/device.conf says false)

If anything here fails, leave the desktops on stable 0.2.2 and fix it in the next maintenance release on canary.