Skip to content

Investigate non-Linux platform testing (macOS, Windows, FreeBSD) #57

@kergoth

Description

@kergoth

Context

We now have container-based testing for Linux distros (Ubuntu, Arch, Chimera) via test/containers/. This issue tracks research into testing options for the remaining platforms where containers aren't a viable option.

macOS

  • UTM / Parallels — Full macOS VMs, manual setup
  • Tart — macOS-native VM tool using Apple Virtualization framework, designed for CI use
  • Anka — Commercial macOS VM solution (Veertu), popular in CI/CD pipelines
  • GitHub Actionsmacos-latest runners available, but limited to what GHA provides (no persistent state)

No container option exists for macOS.

Windows

  • Windows Sandbox — Lightweight, disposable, WIP-level support for automation
  • Windows containers — Limited to Server Core / Nano Server images, not full desktop Windows
  • Vagrant + VirtualBox/Hyper-V — Full VM, heavier but more realistic
  • GitHub Actionswindows-latest runners available

FreeBSD

  • Vagrant boxes — Official FreeBSD boxes exist and are well-maintained
  • bhyve / QEMU — Native FreeBSD hypervisor or QEMU for local VMs
  • Cirrus CI — Supports FreeBSD natively (GitHub Actions does not)
  • FreeBSD Docker images — Community-maintained and limited; not a realistic test environment
  • Firecracker / cloud-hypervisor — Linux-only microVMs, won't help for FreeBSD

Questions to Answer

  • Which platforms are worth automating tests for vs. manual-only?
  • What's the minimum viable test: just script/bootstrap + chezmoi init, or full setup-full?
  • Should we use CI (GHA, Cirrus) or local VMs or both?
  • Cost/complexity trade-offs for each approach

Related Issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions