dev-testing-hypervisor

Name: dev-testing-hypervisor
Availability: InStock
Author: Google

Automate and validate Capsem hypervisor tests across Apple VZ and KVM backends.

68|10|Updated Sep 26, 2025

Search Tags:#testing #ci #unit-tests #kvm #hypervisor #capsem #apple-vz

Ready to run

npx skills add https://github.com/google/capsem --skill dev-testing-hypervisor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-testing-hypervisor
Source: https://github.com/google/capsem/tree/main/skills/dev-testing-hypervisor
Command: npx skills add https://github.com/google/capsem --skill dev-testing-hypervisor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Capsem's hypervisor testing workflow ensures reliable validation of VM configurations across Apple VZ and KVM backends, catching integration issues early and speeding up CI feedback for hypervisor-related changes.

Core Features & Use Cases

Unit tests cover VirtioFS FUSE operations, vsock handshakes, and serial console I/O across backends.
Integration tests validate full VM lifecycle, device setup, config validation, and per-session telemetry in macOS and Linux CI.
Use cases include validating hypervisor abstraction traits, cross-backend CI stability, and CI coverage for both Apple VZ and KVM environments.

Quick Start

Run the hypervisor test suite to validate Apple VZ and KVM backends, focusing on VM boot, VirtioFS, vsock, and serial console behavior.

Frequently Asked Questions about dev-testing-hypervisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I test hypervisor VM lifecycle and VirtioFS across Apple VZ and KVM backends?▼

Hypervisor VM lifecycle and VirtioFS testing across Apple VZ and KVM backends is automated by running unit and integration tests that validate VM boot, FUSE operations, and device setup within macOS and Linux CI environments.

What is the best way to verify vsock handshakes and serial console I/O in a cross-platform CI pipeline?▼

The best way to verify vsock handshakes and serial console I/O in cross-platform CI is to execute targeted unit tests that enforce coverage for both Apple VZ and KVM environments, ensuring consistent behavior across backends.

Does cross-backend hypervisor testing enforce architecture traits and per-session telemetry validation?▼

Yes, cross-backend hypervisor testing enforces architecture traits testing and per-session telemetry validation, ensuring that VM configuration and integration coverage is verified consistently across both macOS and Linux CI.

Can I use automated testing to check VM configuration validation for both KVM and Apple VZ environments?▼

You can use automated integration tests to check VM configuration validation for both KVM and Apple VZ environments, catching integration issues early and speeding up CI feedback for hypervisor-related changes.

When do I need cross-backend hypervisor coverage for Capsem unit and integration tests?▼

You need cross-backend hypervisor coverage when validating hypervisor abstraction traits and CI stability, ensuring that VirtioFS, vsock, and serial console behaviors function reliably across both Apple VZ and KVM backends.