Testing

Two distinct worlds, split accordingly:

Automated — the pvtest suite

The suite itself lives in the pantavisor repo, which documents it: Testing — the harness architecture, running it against the appengine pool or a real device, authoring tests, and the test list.

This repo only assembles the distro that runs it, so what stays here is the build: Building the pvtest distro — the tarball, the fixture containers, and the pantavisor pin (PANTAVISOR_SRCREV).

Manual — hand-driven testing

Building and loading the appengine image, plus the per-feature test plans (auto-recovery, cgroups, container control, IPAM, pvctrl, pvtx, xconnect).

Driving the appengine container itself — starting it, entering namespaces, log locations, pvcurl/pvcontrol recipes — is documented in the pantavisor repo at docs/overview/appengine.md, alongside the pv-appengine code.

Keeping the test list updated

When a pvtest is added, modified, or removed, update the list in the pantavisor repo (pvtest-list.md) and TODO.md. Mark completed tests ✓.