Build, test, and debug workflows for minibox container runtime
Build, test, and debug the minibox container runtime with project-specific workflows.
Use this skill when:
Build all components:
cargo build --all
Build specific components:
cargo build -p minibox # Core library
cargo build -p miniboxd # Daemon
cargo build -p minibox-cli # CLI tool
Release build:
cargo build --release --all
Run all tests:
cargo test --all
Run tests for specific component:
cargo test -p minibox
cargo test -p miniboxd
Run specific test:
cargo test test_name
Run with output:
cargo test -- --nocapture
Format code:
cargo fmt --all
Check formatting:
cargo fmt --all -- --check
Run clippy:
cargo clippy --all -- -D warnings
Check without building:
cargo check --all
cargo fmt --allcargo clippy --all -- -D warningscargo test --allcargo build --release --allCheck dependencies:
cargo tree
Clean build:
cargo clean
cargo build --all
Verbose build:
cargo build --all --verbose
Currently minibox has no test coverage. When adding tests:
Create test module in source file:
#[cfg(test)]
mod tests {
use super::*;
#[test]
fn test_namespace_creation() {
// Test code
}
}
Create integration tests:
mkdir -p tests
# Create tests/integration_test.rs
Key directories:
minibox/ - Core library with container primitivesminiboxd/ - Daemon implementationminibox-cli/ - Command-line interfaceCargo.toml - Workspace configurationBuild helper:
./skills/minibox/build-test/scripts/build.sh
Builds all minibox components with progress output.
Test runner:
./skills/minibox/build-test/scripts/test.sh
Runs all tests with proper output formatting.
Quality checker:
./skills/minibox/build-test/scripts/check.sh
Runs all quality checks (fmt, clippy, tests, compile).
Missing dependencies:
Test failures:
Build performance:
cargo build --release for optimized buildssccache for faster recompilationtarget/ directory size with du -sh target/For comprehensive testing guidance, load references/testing-guide.md which covers: