plugin-contract-tests

To validate Go miner plugins for contract regressions locally, this Skill coordinates a Docker-based test harness that builds the edited plugins and runs the contract suite in isolated containers to detect issues before CI.

Contract tests for miner plugins are validation checks that ensure driver compliance across edits. You should run them when editing miner plugin code under plugin/proto, plugin/antminer, or plugin/virtual directories, or when updating test fixtures.

Yes, this contract testing suite requires Docker to run Go plugin validations, as it coordinates a Docker-based test harness to build the plugins and execute the contract tests in isolated containers for accurate regression detection.

Yes, you can test specific miner plugin drivers like antminer or virtual separately by editing the corresponding plugin code under those directories, which triggers the contract suite to validate regressions across the edited plugin drivers.

If your miner plugin contract test fails in CI but passes locally, running this Skill's Docker-based test harness locally before pushing can detect regressions early by building Go plugins and running the contract suite in isolated containers.

Yes, when modifying miner plugins you may need to update test fixtures in tests/plugin-contract, and this Skill will execute the contract suite against the edited plugins to detect any regressions across drivers.