원클릭으로 Manus에서 모든 스킬 실행

시작하기

machina-testing

스타31

포크24

업데이트2026년 5월 6일 16:47

Use when choosing, adding, listing, or running Machina tests, including targeted Rust tests and workspace validation.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

gevico

gevico/machina

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Machina Testing

All tests live in the standalone tests/ crate named machina-tests.

Commands

Scope	Command
Full test suite	`make test`
Backend tests	`make test-backend`
Frontend tests	`make test-frontend`
Integration tests	`make test-integration`
One Rust test	`cargo test -p machina-tests <filter>`
Format check	`make fmt-check`
Lint	`make clippy`

Adding Tests

Put new tests under tests/src/.
Use existing helpers before adding new harness code.
Name tests after observable behavior, not implementation details.
Cover the expected path, edge cases, and failure cases for new behavior.
For bug fixes, first create or update a regression test that fails on the old behavior.

Running Tests

Start with the narrowest filter that exercises the changed behavior.
Run make fmt-check after code edits.
Run make test before PR submission when behavior changed.
If a test is skipped, verify the skip is part of the intended harness contract and mention it in the result.

Rules

Do not add #[cfg(test)] mod tests inside individual crates.
Do not weaken assertions to match current broken behavior.
Keep expensive QEMU-backed checks behind existing oracle skip behavior.

이 저장소의 다른 Skills

같은 저장소

machina-build

gevico/machina

Use when building Machina, running cargo check, debugging Rust build failures, or deciding which repository build command to run.

2026-05-0631

machina-code-explorer

gevico/machina

Use when finding Machina definitions, call sites, crate boundaries, device models, target code, or QEMU-inspired subsystem mappings.

2026-05-0631

machina-code-reviewer

gevico/machina

Use when reviewing Machina pull requests, local diffs, commits, or mailing-list patch series that may inform Machina changes.

2026-05-0631

machina-issue-helper

gevico/machina

Use when summarizing or preparing to debug Machina GitHub issues, bug reports, feature requests, or reproduction notes.

2026-05-0631

machina-qemu-oracle

gevico/machina

Use when comparing Machina behavior with QEMU, using difftest/oracle tooling, or debugging CPU, interrupt, memory, or device-model parity.

2026-05-0631

name	machina-testing
description	Use when choosing, adding, listing, or running Machina tests, including targeted Rust tests and workspace validation.
license	MIT

Machina Testing

All tests live in the standalone tests/ crate named machina-tests.

Commands

Scope	Command
Full test suite	`make test`
Backend tests	`make test-backend`
Frontend tests	`make test-frontend`
Integration tests	`make test-integration`
One Rust test	`cargo test -p machina-tests <filter>`
Format check	`make fmt-check`
Lint	`make clippy`

Adding Tests

Put new tests under tests/src/.
Use existing helpers before adding new harness code.
Name tests after observable behavior, not implementation details.
Cover the expected path, edge cases, and failure cases for new behavior.
For bug fixes, first create or update a regression test that fails on the old behavior.

Running Tests

Start with the narrowest filter that exercises the changed behavior.
Run make fmt-check after code edits.
Run make test before PR submission when behavior changed.
If a test is skipped, verify the skip is part of the intended harness contract and mention it in the result.

Rules

Do not add #[cfg(test)] mod tests inside individual crates.
Do not weaken assertions to match current broken behavior.
Keep expensive QEMU-backed checks behind existing oracle skip behavior.