菜单
OSCortex kernel driver tests — unit tests in tests/kernel/, QEMU integration in tests/integration/, run via tests/run_all.sh or cargo xtask test. Use when adding or changing kernel drivers, arch shims, platform init, or docs/hardware compliance.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit and clean OSCortex for redundancy, AI slop, dead pivots, and missing reusability. Trigger on: cleanup, audit, duplicate code, technical debt, refactor, bloat, pivot, remove old code, one path, code reusability, or before large features. Excludes landing/.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Enforce A2UI protocol compliance for all OSCortex UI components. Trigger when: adding a new Osc* widget, creating a new interactive component, modifying the oscortex_ui package, or any question about A2UI support. Ensures every new component has an A2UI renderer mapping and is exported correctly.
Canonical OSCortex OS architecture — kernel vs Flutter userspace, process isolation, shell vs apps, runtime install model. Use when designing features, refactoring boot/app launch, writing docs, or any question about how OSCortex should work (not legacy hacks).
OSCortex Git branching, CI gates, PR compliance, and production release flow. Use when committing, pushing, opening PRs, merging to develop/main, releasing ISOs, setting up GitHub Actions, or any question about which branch to work on.
OSCortex hardware and driver model — display/GPU path, device classes, syscalls, multi-arch rules, CDP WASM drivers. Use when adding or changing drivers, input, audio, storage, net, compositor backends, or any question about hardware support vs CPU porting.
| name | oscortex-kernel-tests |
| description | OSCortex kernel driver tests — unit tests in tests/kernel/, QEMU integration in tests/integration/, run via tests/run_all.sh or cargo xtask test. Use when adding or changing kernel drivers, arch shims, platform init, or docs/hardware compliance. |
Read first: tests/README.md · docs/hardware.txt
Related skills: oscortex-hardware · oscortex-architecture · oscortex-ci-cd · codebase-audit-cleanup
# Fast — host unit tests only (any machine)
tests/run_all.sh
cargo xtask test
# Full — unit + QEMU driver smoke (x86_64, builds ISO)
tests/run_all.sh --qemu
cargo xtask test-qemu
| Path | Purpose |
|---|---|
tests/kernel/ | Host cargo test — pure logic from kernel/src/drivers/common/ |
tests/integration/qemu_drivers.sh | Boot ISO, grep serial for driver ready markers |
tests/run_all.sh | Unified runner |
kernel/src/drivers/common/ | Testable pure helpers — keep driver math here |
drivers/common/, add/update unit test in tests/kernel/unit/.drivers/platform.rs, list in docs/hardware.txt, extend tests/kernel/unit/driver_manifest.rs if needed.tests/integration/qemu_drivers.sh if bring-up critical.tests/run_all.sh before finishing driver work.Tests include kernel sources directly (no full no_std host build):
#[path = "../../../kernel/src/drivers/common/vring.rs"]
mod vring;
Do not duplicate layout math in the test crate — change drivers/common/ and tests follow.
Expected in QEMU serial output:
[virtio-blk] ready[virtio-net] ready + [virtio-net] self-test TX completion OK[NVMe][Input] PS/2 enabled[USB-HID] WM route OK (HID parse → WM self-test; runs on every x86 boot)[USB] XHCI ready or [USB] N XHCI controller(s) mapped and reset[USB] XHCI runtime started (command/event rings programmed; enumeration polled on vsync)[smoltcp] TCP/IP stack initialised[net] DHCP self-test OK or timeout (static IP fallback OK)[net] TCP self-test connect OK or connect skippedAlso run on every CI/local check:
tests/integration/kernel_build.sh — x86_64-unknown-none cross-build on host (works on Apple Silicon Macs)[USB-HID] live key from -device usb-kbd) — xHCI runtime rings up but full EP0/HID enumeration still WIPDocument gaps in docs/hardware.txt — do not claim test coverage that does not exist.