local-e2e-testing

Build Bluefin OCI images, install them to disks, and launch QEMU VMs for local end-to-end testing.

134|27|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/projectbluefin/dakota --skill local-e2e-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-e2e-testing
Source: https://github.com/projectbluefin/dakota/tree/main/.opencode/skills/local-e2e-testing
Command: npx skills add https://github.com/projectbluefin/dakota --skill local-e2e-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the local development workflow for Bluefin, enabling developers to build the OCI image, test it in a VM, and iterate quickly without relying on remote CI.

Core Features & Use Cases

  • Local Build & Boot: Compiles the Bluefin OCI image and boots it in a QEMU VM using a single command.
  • Iterative Development: Facilitates rapid testing of changes by rebuilding and re-booting the VM efficiently.
  • BuildStream Integration: Provides direct access to BuildStream commands within a containerized environment for detailed build inspection and management.
  • Local OTA Updates: Supports pushing image updates to a running VM via a local OCI registry for a full development loop.

Quick Start

Use the local-e2e-testing skill to build the OCI image, install it to a bootable disk, and launch a QEMU VM.

Frequently Asked Questions about local-e2e-testing

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

FAQPage Schema
How do I build and test a Bluefin OCI image locally without remote CI?

Build and test a Bluefin OCI image locally by compiling the image, installing it to a bootable disk, and launching a QEMU virtual machine to verify the changes without relying on remote CI.

How do I test Over-The-Air updates for an OS image in a local QEMU VM?

Test Over-The-Air updates locally by pushing image updates to a running QEMU virtual machine via a private local OCI registry, allowing you to verify the full OTA development loop.

Can I use BuildStream inside a container to inspect Bluefin image builds?

Yes, local end-to-end testing provides direct access to BuildStream commands within a containerized environment, enabling detailed build inspection and management for the Bluefin image.

What is the best way to iterate quickly when developing an OCI operating system image?

Iterate quickly on an OCI operating system image by using efficient rebuilds that compile changes and re-boot a QEMU virtual machine rapidly, streamlining the local development workflow.

Does local end-to-end testing support pushing updates directly to a running virtual machine?

Yes, local end-to-end testing supports pushing image updates directly to a running QEMU virtual machine by utilizing a local OCI registry to facilitate the update process.