Skip to main content

plugin-contract-tests

Verify miner-driver behavior after protocol or contract-fixture changes.

Source facts

Repository
block/proto-fleet
Last source activity
September 18, 2026 at 19:52
Detected SKILL.md language
English
Stars
57
Forks
18

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
plugin-contract-tests
description
Verify miner-driver behavior after protocol or contract-fixture changes.
# plugin-contract-tests The contract suite (`tests/plugin-contract/`) runs each miner test in its own container so port-bound mocks (`fake-antminer`, ASIC-rs harnesses) don't collide. Pre-push lefthook does **not** run it. Server `just lint` does **not** run it. CI runs it on PR via `protofleet-contract-checks.yml`, but by then it's a feedback delay. ## What to do 1. After plugin or fixture edits, run `just test-contract` from the repo root. It builds the Go plugins, compiles the test binary once, and runs `TestAntminerStock`, `TestAntminerVNish`, and `TestWhatsMinerStock` in isolated containers. For ASIC-rs platform prerequisites, including the current macOS recipe blocker, read [build guidance](../asicrs-build/SKILL.md). 2. Surface the failing test name and the plugin under test (the test names map to the miner model, not the plugin module — read the suite output carefully). 3. If the change is a deliberate behavior change, add or update a contract testdata fixture under `tests/plugin-contract/testdata/` or the relevant miner harness — don't loosen the test to make it pass. ## What to avoid - Don't run the contract tests outside Docker. The harness assumes container port isolation; running on the host will race with anything bound to 4028 or 80.
View on GitHub