免费在 GitHub 公开

emulators-system-test-builder

Design and implement unit, conformance, integration, timing, boot, trace, video, audio, and regression tests for EMULATORS processors, chips, peripherals, and complete machines. Use when creating a verification strategy for a new emulator, converting hardware documentation into tests, adding diagnostic programs or golden artifacts, measuring behavioral coverage, or proving that components interact correctly.

中文简介正在准备中。当前显示原文说明。

Commnets/EMULATORS

查看安装方法

包含的文件（3）

SKILL.md3.0 KB
agents/openai.yaml226 B
references/validation-matrix.md1.3 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Build EMULATORS System Tests

When compiling, testing, or executing on Windows, use $emulators-windows-build-runtime.

Required Context

Read references/validation-matrix.md.
Read .codex/skills/emulators-new-machine/references/workspace-artifacts.md. Store working validation matrices, acquisition state, and intermediate evidence in the active .codex/work/ scope or .codex/tmp/<task>/ as appropriate, never in docs/.
Inspect the implementation contract, authoritative hardware sources, nearby tests under tests/, and diagnostic programs under emulators/*Programs/.
Use $emulators-framework-cpp-style for C++ tests. Use $emulators-debug-log-audit when instruction/cycle traces are part of the evidence.
Use the relevant CPU, chip, I/O, memory-map, video, sound, or system audit skill when its trigger matches.

Workflow

Define observable claims before choosing the test mechanism. Map every important claim to a source, stimulus, expected observation, tolerance, and test layer.
Build the cheapest reliable layer first: unit, component, integration, diagnostic program, then boot or application test.
Derive expectations independently from documentation, known vectors, captured reference traces, or manually justified calculations. Never duplicate the implementation formula as the oracle.
Make time explicit. Record sampling points, preconditions, cycles elapsed, intermediate events, and final state for timing-sensitive tests.
Control nondeterminism: seed randomness, replace host time, provide fixed input streams, isolate filesystem state, and define audio/video tolerances.
Test boundaries and negative paths before declaring coverage complete.
Add regression tests for every confirmed defect when a stable observable exists.
Build and run the narrowest target, then the relevant integration target. Preserve raw failure evidence when a discrepancy remains.

Evidence Standards

Prefer exact state or ordered trace assertions over screenshots and log substring matching.
Use golden video or audio only with documented format, capture window, tolerance, and update policy.
Distinguish structural opcode/register coverage from behavioral and timing coverage.
Treat a passing boot as a smoke test, not proof of component accuracy.
Mark unavailable ROMs, proprietary suites, hardware captures, or external vectors as evidence gaps.

Completion Evidence

Report the validation matrix, new tests and assets, commands and results, coverage by behavior class, environmental dependencies, unresolved mismatches, and fidelity claims the evidence actually supports.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

c64-1541-audit

免费

Validate Commodore 1540/1541/1541C/1541-II compatible disk-drive behavior in EMULATORS, including IEC serial bus protocol, device numbers, KERNAL traps, CBM DOS commands/status, D64 image parsing, BAM/directory/file chains, PETSCII filenames, 6502 drive CPU/ROM/RAM expectations, 6522 VIA wiring, GCR/track/sector geometry, motor/head timing, and compatibility boundaries for 1541-like devices. Use when Codex reviews or edits C64, VIC-20, C264, COMMODORE disk, serial I/O, D64, CBM DOS, IEC, VIA, GCR, or 1541 drive code.

中文简介正在准备中。当前显示原文说明。