MIL-013: Windows Sandbox run of the executable passed

The Windows executable passed the smoke test in Windows Sandbox: 5 of 5
runs (window, list override, known button, progress file). Review record
RC-080 (Go) closes criterion 7 of MIL-013 and the open condition of RC-072
on the smoke test.

Task: MIL-013#8
This commit is contained in:
2026-10-15 10:17:52 +08:00
parent a4e55541c1
commit 6e3fcf8aa3
4 changed files with 50 additions and 3 deletions
+1 -1
View File
@@ -164,7 +164,7 @@ docker run --rm -v "$PWD:/repo:ro" flash-card-debian bash /repo/tools/docker/in-
On Windows PowerShell write `${PWD}` for `$PWD`. The repository is mounted read-only and copied inside the container.
- The desktop is Xvfb with GNOME's window manager (mutter). GNOME Shell is tried first and does not start in a container (it needs a login manager), so the scripts fall back to mutter and print which one ran.
- The Windows executable is checked in **Windows Sandbox** (Windows 11 Pro, feature enabled): `powershell -File tools\sandbox\run.ps1 -Runs 5` after `python tools/build_executable.py`. The sandbox shows its own window while it runs; the click is made inside the sandbox.
- The Windows executable is checked in **Windows Sandbox** (Windows 11 Pro, feature enabled; the version 0.2.0 build passed 5 of 5 runs, see RC-080): `powershell -File tools\sandbox\run.ps1 -Runs 5` after `python tools/build_executable.py`. The sandbox shows its own window while it runs; the click is made inside the sandbox.
- Not covered: macOS (it cannot be run in Docker on Windows or Linux and Apple's licence allows it only on Apple hardware), and Windows itself in the Debian container.
## 📄 License