HyperGery Validation

v0.8.0 — Remote Cluster Workflows (in development, overnight run 2026-06-05)

Automated validation after implementing Fases 2–5 (Hub staging cleanup, Remote VM details + Command Queue UI, Labs workspace, Lab power actions + polish), on top of the already-validated Fase 1 (Remote VM Power Control, 260 tests, real PC ↔ Lenovo smoke):

QT_QPA_PLATFORM=offscreen ~/.venvs/hypergery/bin/python -m unittest discover -s tests — 315 tests OK.
python3 -m unittest discover -s tests — 315 tests OK (Qt tests skipped cleanly without PySide6).
python3 -m compileall hypergery-ubuntu OK.
bash -n on all 9 shell scripts OK.
docker compose config OK.
Final audit grep: no secrets, passwords, private keys, TODO/FIXME, or stale "planned for v0.8" promises in code/docs (settings callouts re-worded; remaining "arrives in v0.8" mentions are historical v0.7 notes or refer to post-v0.8 features).
Removed stale MagicMock/ test-pollution directory from the repo root; confirmed the current suite does not recreate it.

New v0.8 test coverage includes: staging cleanup rules (dry-run default, active/recent/symlink protection, traversal), cleanup CLI confirm flow, command listing filters/limits (store + HTTP + client), agent XML interface parsing and inventory fallback, remote VM details panel with staleness warning, Commands page rendering/filters/copy/read-only checks, lab manifest vm_roles migration, lab workspace aggregation (local + remote + manifest-only), lab power planning and role ordering, lab action confirmations and partial-failure reporting, and Hub-offline / empty-state rendering for every new page.

Pending for tomorrow (manual smoke, PC ↔ Lenovo, see §13.4 of the v0.8 plan): remote inventory/start/shutdown/force-off in real hardware, Command Queue with real commands, staging cleanup dry-run + confirm over a fake orphan package, Labs workspace with real VMs, Start/Shutdown Lab, console local VNC/SPICE, Diagnostics, Settings. No release, no tag, no merge to main until the user confirms "smoke OK".

v0.7.0 — Visual Refresh & Hub Transfer close-out (2026-06-05)

QT_QPA_PLATFORM=offscreen ~/.venvs/hypergery/bin/python -m unittest discover -s tests ran 249 tests OK.
python3 -m unittest discover -s tests ran 249 tests OK with Qt tests skipped cleanly.
python3 -m compileall hypergery-ubuntu OK.
bash -n on all 9 shell scripts OK (including start-second-host.sh and install-agent-user-service.sh).
docker compose config OK.
Hub package staging endpoints smoke-tested against the NAS Hub (upload → list → delete).
Real two-host Hub Transfer E2E migrations passed on physical hardware (source gerard-MS-7E26 → target gery-Lenovo-ideapad-330S-14IKB via Hub on the NAS):
- small-disk migration → done
- migration including a 2.8 GiB ISO → done
- migration with a ~5.8 GiB VM disk → done, target started after import
In every E2E run: source VM untouched, target imported with regenerated UUID/MAC, Hub staging copy deleted after import (hub_package_deleted: true), target temp directory cleaned.
True live RAM migration remains intentionally not included in v0.7.0.

HyperGery Hub Docker

Validate the Docker deployment files without starting the service:

cd docker
docker compose config
docker compose build

When running on the NAS:

curl http://192.168.1.150:8765/health
curl http://192.168.1.150:8765/hosts

Agent smoke on Ubuntu:

export HYPERGERY_HUB_URL=http://192.168.1.150:8765
export HYPERGERY_HOST_ID=ubuntu-hyperv
export HYPERGERY_HOST_NAME="Ubuntu Hyper-V"
export HYPERGERY_NAS_STAGING_PATH=/mnt/hypergery-nas/hypergery
python -m hypergery_ubuntu.cli agent once
python -m hypergery_ubuntu.cli host list --hub-url http://192.168.1.150:8765
python -m hypergery_ubuntu.cli hub vms --hub-url http://192.168.1.150:8765

Docker/Hub/Agent smoke on prepared host (2026-06-05):

NAS Clone Migration local E2E smoke on prepared host (2026-06-05):

NAS Clone Migration two-physical-host smoke on prepared hosts (2026-06-05):

v0.6.0 close-out check on prepared host (2026-06-05):

v0.6.0 — NAS Clone Migration Validation Plan

v0.6.0 final validation proves NAS Clone Migration behavior without deleting the source VM or original disks.

Required automated checks:

cd hypergery-ubuntu && python3 -m unittest discover -s tests
cd hypergery-ubuntu && ~/.venvs/hypergery/bin/python -m unittest discover -s tests
python3 -m compileall hypergery-ubuntu
bash -n scripts/dev-run.sh scripts/bootstrap-ubuntu.sh scripts/preflight.sh scripts/acceptance-ubuntu.sh scripts/acceptance-real-host.sh scripts/install-ubuntu-deps.sh scripts/install-desktop-launcher.sh

First-run bootstrap smoke:

./scripts/dev-run.sh --check-only prints system/package/service/group/Python readiness and does not install.
./scripts/dev-run.sh --no-install exits clearly if anything is missing.
On a prepared host, ./scripts/dev-run.sh --no-install runs preflight and starts the Qt app without reinstalling.
On a fresh Ubuntu laptop, ./scripts/dev-run.sh asks before installing packages.
./scripts/dev-run.sh --install installs/fixes missing items without the interactive question, while sudo/pkexec still prompts normally.
If kvm/libvirt membership changes, the script prints the logout/login warning.
The venv is created at ~/.venvs/hypergery with --copies, not inside the repo.

Bootstrap smoke on prepared host (2026-06-04):

./scripts/dev-run.sh --check-only reported no missing system tools, no inactive services, no missing groups, and Python environment ready.
timeout 8s ./scripts/dev-run.sh --no-install did not reinstall anything, ran preflight successfully, and reached Qt app startup before the controlled timeout.

Required local smoke:

Registry/agent local smoke on prepared host (2026-06-04):

Started local registry with a temporary SQLite DB on 127.0.0.1:18765.
Ran agent once with a temporary config and registered local-smoke.
Listed hosts through CLI and confirmed local-smoke was present.
Queued a safe ping command through host test local-smoke.
Ran agent once again and confirmed command status done with pong=true.

Migration package unit/CLI smoke on prepared host (2026-06-04):

migration_preflight() blocks a running VM with source_will_be_deleted=false.
export_vm_package() creates manifest.json, domain.xml, copied disk/ISO assets, checksums, lab metadata, and migration log in migrations/<migration_id>/.
validate_vm_package() accepts a clean package and reports checksum mismatch after asset tampering.
import_vm_package() rewrites target VM name, UUID, MAC address, disk paths, ISO paths, network metadata, and lab association using a simulated backend.
CLI migrate preflight returns JSON and preserves source_will_be_deleted=false.
Agent preflight command runs VM migration preflight and fails safely for running VMs.
Agent receive_vm_package validates only packages inside configured NAS staging.
Agent import_vm_package calls the package import flow and blocks paths outside staging.
Qt Live Migration dialog runs VM preflight and keeps package creation disabled for running VMs.

Recommended real NAS/two-host smoke:

Blocking conditions:

Running VM copy must be blocked unless a real safe libvirt/QEMU strategy is implemented.
Missing disks are critical errors.
Missing ISO is an error when include_iso=True.
Target host offline, missing staging path, insufficient space, and target name conflicts must block Start Migration.
No v0.6.0 release may be created until this checklist is completed.

v0.5.0 RC — Automated Tests Status

Run with system Python (PySide6 not required):

cd hypergery-ubuntu && python3 -m unittest discover -s tests
# Expected: Ran 131 tests — OK (skipped=4)

Run inside the venv (all tests including Qt):

cd hypergery-ubuntu && ~/.venvs/hypergery/bin/python -m unittest discover -s tests
# Expected: Ran 131 tests — OK

The 4 skipped tests are Qt widget tests that require PySide6. They pass cleanly in the venv.

New in v0.5.0: 10 additional tests covering build_lab_topology (empty, live VMs, not-created VMs, cross-lab exclusion, deduplication, JSON export), CLI template update, CLI lab-topology, CLI lab-instantiate --dry-run, and libvirt KiB memory parsing.

Offscreen Qt smoke (2026-06-03):

QT_QPA_PLATFORM=offscreen python -c "
from PySide6.QtWidgets import QApplication; import sys
from hypergery_ubuntu.ui_qt.topology import LabTopologyWidget
from hypergery_ubuntu.ui_qt.lab_helpers import build_lab_topology
from hypergery_ubuntu.backend import VmSummary
app = QApplication(sys.argv)
w = LabTopologyWidget(); w.resize(500, 300)
lab = {'lab_id': 'asr-lab', 'name': 'ASR Lab', 'network_mode': 'isolated',
       'network_id': 'hg-net-asr-lab-isolated', 'subnet': '192.168.30.0/24',
       'bridge_name': 'hgbr1234567', 'vms': ['server', 'ghost']}
vms = [VmSummary(name='server', state='running', lab_id='asr-lab', ram_mib=4096, vcpus=2)]
w.set_topology(build_lab_topology(lab, vms)); w.show()
print(w.grab().width())  # should print 500
"

Result: widget renders at 500×300 px, 2 VM nodes (server=live/running, ghost=not created). OK.

v0.5.0 RC — Manual/Host Smoke Validated (2026-06-04)

Validated on a real Ubuntu/KVM/libvirt host from develop. The UI-specific interactions were exercised with the real PySide6 widgets using Qt's test driver/offscreen rendering because the active desktop session was Wayland and no desktop automation/screenshot tools were available to the agent. Real libvirt resources were created, started, paused, force-powered-off, opened through the console flow, and cleaned up.

Preparation

git switch develop
git pull origin develop
./scripts/preflight.sh
System Python tests: Ran 131 tests — OK
Venv PySide6 tests: Ran 131 tests — OK
python3 -m compileall hypergery-ubuntu
bash -n for all release scripts
./scripts/dev-run.sh launched without immediate traceback; stopped by controlled timeout after startup.

Lab Topology View

Created lab hg-v05-topology-lab.
Created real VM hg-v05-topology-vm from a local Ubuntu server ISO.
Started VM and confirmed running via libvirt.
Suspended/resumed VM and confirmed paused topology state.
Force-powered VM off and confirmed shut off.
Rendered LabTopologyWidget with network node on the left and VM nodes on the right.
Confirmed colors: running green, shutoff gray, paused amber, not-created slate.
Clicked VM node via Qt test driver and confirmed the widget emitted selection for hg-v05-topology-vm.
No traceback.

Planned VM Editor

Created lab template hg-v05-asr-template.
Added planned VMs hg-v05-ad-server and hg-v05-client.
Opened planned VM edit dialog and edited name, RAM, vCPUs, disk, role, template_id, and notes.
Duplicate planned VM name was blocked.
Valid changes were saved and reflected in the table.

ISO Reuse

Opened the instantiation wizard for hg-v05-asr-template.
Confirmed missing ISO status label lists required VMs.
Applied the same local Ubuntu server ISO once via "Apply same ISO to all VMs...".
Confirmed all required ISO rows were filled and status label cleared.

Instantiate Lab Template

Instantiated hg-v05-asr-lab from hg-v05-asr-template.
Created real VMs hg-v05-ad-server-renamed and hg-v05-client.
Confirmed templates_used = ["hg-v05-asr-template"].
Confirmed backend activity log entries in ~/.local/state/hypergery/logs/hypergery.log.
Started hg-v05-ad-server-renamed.
Opened console with virt-viewer flow.
ACPI shutdown did not complete within the smoke timeout; force-off succeeded and VM returned to shut off.

Cleanup Preview

Opened CleanupPreviewDialog.
Confirmed it lists HyperGery VMs, labs, VM templates, and lab templates.
Confirmed the dialog is read-only and does not mutate resource counts.

CLI

lab-topology hg-v05-topology-lab returned valid JSON.
Found and fixed a real issue: ram_mib was 0 because libvirt returns memory as KiB in dumpxml.
lab-topology hg-v05-topology-lab then returned ram_mib: 1024 for the real test VM.
lab-instantiate hg-v05-asr-template hg-v05-cli-dry-run --dry-run returned JSON and created no lab/VM resources. It correctly reported missing ISO errors because that exact command does not provide ISO mappings.
template update lab hg-v05-asr-template --set notes="v0.5 smoke test" updated the template.

Cleanup

Deleted only VMs/labs/templates with prefix hg-v05.
Deleted only HyperGery-managed disks through delete-vm --delete-disks.
Removed test libvirt networks hg-net-hg-v05-asr-lab and hg-net-hg-v05-topology-lab.
Final virsh --connect qemu:///system list --all showed only the pre-existing ubuntu VM.
No hg-v05-* labs/templates/disks remained under ~/.local/share/hypergery.

Bug Fixed During Validation

HyperGeryBackend.get_vm() now converts libvirt memory units to MiB. This fixes topology/CLI reporting for hosts where virsh dumpxml normalizes <memory> to unit="KiB".

v0.5.0 RC — Manual Smoke Checklist

Run from the Qt UI (python -m hypergery_ubuntu inside the venv). Requires a real Ubuntu KVM/libvirt host.

Lab Topology

Create or select a lab with at least one VM (e.g. hg-v04-asr-lab from v0.4.0 smoke)
Click the Topology sub-tab in the Lab Details panel
Network node visible on the left with network name, mode, and subnet
VM node(s) visible on the right, colour-coded by state
Start a VM → topology refreshes after next Refresh → node turns green
Click a VM node → VM selected in the main list, Details tab activates

Planned VM Editor (improved)

Select a lab template → Click Edit
Planned VMs table shows columns: Name, Role, OS, RAM MiB, vCPUs, Disk GB, Display, ISO req.
Double-click a VM row → Edit dialog opens with fields pre-filled
Change RAM, click OK → table updates immediately
Add a VM with the same name as an existing one → duplicate error shown
Remove a VM row → VM count decreases

ISO Reuse in Wizard

Select a lab template with ≥2 planned VMs requiring ISO
Click Create Lab from Template → Page 2 (ISO Mapping)
Click Apply same ISO to all VMs… → browse once → all rows filled
Status label disappears when all required ISOs are set

Resource Overview

Click Resources… button in toolbar
Dialog shows all VMs, labs, VM templates, lab templates
No delete buttons — read-only
Close button works

CLI — template update

python -m hypergery_ubuntu.cli template update vm hg-v04-ubuntu-template --set ram_mib=8192
# expected: JSON output with ram_mib=8192

JSON returned; ram_mib updated in the file

CLI — lab-topology

python -m hypergery_ubuntu.cli lab-topology hg-v04-asr-lab
# expected: JSON with lab_id, subnet, vms list

JSON returned; vms list present

CLI — lab-instantiate dry-run

python -m hypergery_ubuntu.cli lab-instantiate hg-v04-asr-template "ASR Test" \
  --iso hg-v04-ad-server=/path/to/ubuntu.iso \
  --iso hg-v04-client=/path/to/ubuntu.iso \
  --dry-run
# expected: JSON with dry_run=true, errors=[], lab=null

dry_run=true in response; no lab created

Activity Log

All topology-tab switches, resource overview open, template edits appear in log

Not smoke-tested (requires extended setup)

Topology node click on a real running VM
Per-VM progress during lab instantiation (not yet implemented)

v0.4.0 — Automated Tests Status

Run with system Python (PySide6 not required):

cd hypergery-ubuntu && python3 -m unittest discover -s tests
# Expected: Ran 121 tests — OK (skipped=4)

Run inside the venv (all tests including Qt):

cd hypergery-ubuntu && ~/.venvs/hypergery/bin/python -m unittest discover -s tests
# Expected: Ran 121 tests — OK

The 4 skipped tests are Qt widget tests that require PySide6. They pass cleanly in the venv.

New in v0.4.0: 20 additional tests covering instantiate_lab_template (dry_run, ISO validation, rollback, iso_required=False), update_vm/lab_template, planned VM validation (duplicate names, empty names), and _resolve_planned_vm precedence.

v0.4.0 — Manual Smoke Validated (2026-06-03)

Run from the Qt UI (python -m hypergery_ubuntu inside the venv). Validated on a real Ubuntu KVM/libvirt host.

Lab Template Instantiation

Edit VM Template

Select VM template → Click Edit → Change RAM, add note → Save
Detail panel updates with new values

Edit Lab Template + Planned VMs

Select hg-v04-asr-template → Click Edit → Add/remove planned VMs → Save
Detail panel reflects updated VM count

Lab Duplicate with VM Cloning

Select lab with VMs → Click Duplicate Lab → Clone VMs checkbox is enabled
Clone VMs with disk cloning (not completed in this smoke — requires all VMs shut off simultaneously; defer to extended test)

Cleanup

Delete lab and VMs; delete both templates
Activity log records all operations; no tracebacks

Not smoke-tested (requires extended setup)

CLI template update / template instantiate (not yet implemented)
Rollback from partial VM creation failure with a real ISO
Duplicate Lab with Clone VMs end-to-end (disk clone path)

v0.3.0 — Manual Smoke Validated (2026-06-03)

Run from the Qt UI (python -m hypergery_ubuntu inside the venv).

Lab Manager

Create lab hg-v03-asr with network=isolated
Create lab hg-v03-par with network=nat
Confirm subnets differ in Lab Details panel
Rename hg-v03-par display name (lab_id unchanged)
Export hg-v03-asr to /tmp/hg-v03-asr.json
Import /tmp/hg-v03-asr.json with new id hg-v03-asr-copy
Verify hg-v03-asr-copy appears in the lab list with a different subnet
Delete all temporary labs

Templates Manager

Activity Log

All above operations appear in the Activity Log panel
Copy log to clipboard works

Not smoke-tested (requires real ISO or KVM host)

Create VM from Template end-to-end with a real ISO
Verify templates_used in the lab JSON after VM creation
Console, snapshots, clone on a real VM

v0.3.0 Backend — Already Validated by Tests

Lab ID validation and normalization.
Lab create/list/show/rename/delete/export/import.
Legacy lab manifest migration to schema version 2.
Portable lab export without private disk/ISO paths.
Lab bridge generation with Linux interface length limits.
Lab subnet allocation avoiding 192.168.122.0/24 and collisions.
VM template create/list/show/delete/export/import.
Lab template create/list/show/delete/export/import.
Template ID preview/normalization.
Wizard defaults mapping (os_type, ram_mib, vcpus, disk_gb, network_mode, display).
Import collision rejection (no silent overwrite).
Delete non-existent template raises clear error.
CLI coverage for lab and template commands.

v0.3.0 Qt Lab Manager — Validated by Unit Tests

Lab preview helper generates lab_id, network ID, bridge, and subnet before creation.
Preview validation rejects duplicate lab IDs.
VM filter helper supports All VMs and Selected Lab.
VM count combines live libvirt summaries and manifest entries.

Not yet implemented (v0.4 target)

Auto-create planned VMs from lab template.
Edit templates in place.
Clone VM disks during lab duplicate.
Delete Lab with VMs included.

v0.2.0 PySide6 UI Validation Status

v0.2.0 was manually validated from the PySide6/Qt UI on a real Ubuntu KVM/libvirt host.

Validated:

PySide6/Qt UI starts from the venv/NAS setup.
Host preflight reaches libvirt when the user has effective libvirt group membership.
New VM wizard creates hg-v02-qt-test from a real ISO.
Start works and the VM reaches running.
Console opens through virt-viewer and displays the installer.
Power-off path works through ACPI Shutdown or Force Off, depending on guest responsiveness.
Snapshots create/list/revert/delete work from the UI.
Clone to hg-v02-qt-clone works.
Safe delete of test and clone works.
No hg-v02-qt-test or hg-v02-qt-clone VMs/disks remain after validation.
VM state loading works with localized virsh output such as ejecutando.

v0.2.0 Manual UI Checklist

Use real names:

hg-v02-qt-test
hg-v02-qt-clone

Run:

git switch develop
git pull origin develop
source ~/.venvs/hypergery/bin/activate
./scripts/preflight.sh
./scripts/dev-run.sh

If the current login session has not inherited the libvirt group yet, either log out and back in or run:

sg libvirt -c 'cd /path/to/miversiondevirtualbox && source ~/.venvs/hypergery/bin/activate && ./scripts/dev-run.sh'

Checklist:

v0.1.0 Validation

HyperGery v0.1.0 was validated on a real Ubuntu KVM/libvirt host.

The validation covered:

Real preflight against /dev/kvm, libvirt, QEMU tools, and viewer tools.
Real VM creation from an Ubuntu ISO.
Real qcow2 disk creation.
Real libvirt network creation for hg-net-default-lab.
Real SPICE console opened with virt-viewer.
Real snapshots: create, list, revert, delete.
Real clone of a stopped VM with an independent qcow2 disk.
Safe delete of managed test VMs and disks.

Repeat CLI acceptance:

./scripts/preflight.sh
./scripts/acceptance-ubuntu.sh --iso /path/to/ubuntu-or-debian.iso --name hg-acceptance-ubuntu-test

Running tests

System Python (no PySide6)

python3 -m unittest discover -s hypergery-ubuntu/tests

Expected: all non-Qt tests pass; test_qt_ui and test_qt_lab_helpers classes that require PySide6 are skipped (not errors). Overall result: OK (skipped=N).

Venv with PySide6

~/.venvs/hypergery/bin/python -m unittest discover -s tests

Expected: all tests pass including Qt UI tests.

Templates Manager smoke test (v0.3.0)

Run this after starting the Qt UI (python -m hypergery_ubuntu inside the venv).

Open the Templates tab in the left panel.
Create VM template
- Click New VM Template.
- Enter Name: HG v03 Ubuntu Template.
- Verify Template ID preview shows hg-v03-ubuntu-template.
- Set OS=linux, RAM=4096, vCPUs=2, Disk=40, Network=nat, Display=spice.
- Click Create — template appears in the VM Templates table.
Create Lab template
- Click New Lab Template.
- Enter Name: HG v03 ASR Template.
- Verify Template ID preview shows hg-v03-asr-template.
- Set Network=isolated.
- Click Create — template appears in the Lab Templates table.
Select and inspect
- Click on hg-v03-ubuntu-template — detail panel shows all fields, Create VM from Template button activates.
- Click on hg-v03-asr-template — detail panel updates, Create Lab from Template button activates.
Create VM from Template
- Select hg-v03-ubuntu-template.
- Click Create VM from Template.
- Wizard opens with RAM=4096, vCPUs=2, Disk=40, Network=nat, Display=spice pre-filled.
- Enter a VM name and a valid local ISO path.
- Complete the wizard — VM is created; activity log shows "Creating VM … from template".
- Open the Instances tab — VM appears in the list.
- (Optional) Open the lab manifest JSON and verify templates_used contains hg-v03-ubuntu-template.
Create Lab from Template
- Select hg-v03-asr-template.
- Click Create Lab from Template.
- Dialog opens with network=isolated pre-filled, preview shows lab_id/bridge/subnet.
- Enter a lab name (e.g. ASR Instance 01).
- Click Create Lab — lab appears in the Labs table; activity log shows "Created lab … from template".
- Verify templates_used in the lab manifest.
Export VM template
- Select hg-v03-ubuntu-template.
- Click Export — choose a path like /tmp/hg-v03-ubuntu-template.json.
- File is created with valid JSON.
Import VM template (collision)
- With hg-v03-ubuntu-template present, click Import and select the same file.
- An error is shown: "VM template already exists" — no silent overwrite.
Delete test artifacts
- Delete hg-v03-ubuntu-template and hg-v03-asr-template by typing their IDs.
- Delete the lab created in step 6.
- Tables are empty after deletion.

Expected: no tracebacks, activity log records each operation, UI stays responsive.

FilesExpand file tree

VALIDATION.md

Latest commit

History

VALIDATION.md

File metadata and controls

HyperGery Validation

v0.8.0 — Remote Cluster Workflows (in development, overnight run 2026-06-05)

v0.7.0 — Visual Refresh & Hub Transfer close-out (2026-06-05)

HyperGery Hub Docker

v0.6.0 — NAS Clone Migration Validation Plan

v0.5.0 RC — Automated Tests Status

v0.5.0 RC — Manual/Host Smoke Validated (2026-06-04)

Preparation

Lab Topology View

Planned VM Editor

ISO Reuse

Instantiate Lab Template

Cleanup Preview

CLI

Cleanup

Bug Fixed During Validation

v0.5.0 RC — Manual Smoke Checklist

Lab Topology

Planned VM Editor (improved)

ISO Reuse in Wizard

Resource Overview

CLI — template update

CLI — lab-topology

CLI — lab-instantiate dry-run

Activity Log

Not smoke-tested (requires extended setup)

v0.4.0 — Automated Tests Status

v0.4.0 — Manual Smoke Validated (2026-06-03)

Lab Template Instantiation

Edit VM Template

Edit Lab Template + Planned VMs

Lab Duplicate with VM Cloning

Cleanup

Not smoke-tested (requires extended setup)

v0.3.0 — Manual Smoke Validated (2026-06-03)

Lab Manager

Templates Manager

Activity Log

Not smoke-tested (requires real ISO or KVM host)

v0.3.0 Backend — Already Validated by Tests

v0.3.0 Qt Lab Manager — Validated by Unit Tests

Not yet implemented (v0.4 target)

v0.2.0 PySide6 UI Validation Status

v0.2.0 Manual UI Checklist

v0.1.0 Validation

Running tests

System Python (no PySide6)

Venv with PySide6

Templates Manager smoke test (v0.3.0)