mockery
Mockery Mock Generation Workflow
When to Activate This Skill
- A new interface is added to
internal/application/ports/ - A test file contains a manually-written mock/stub for a ports interface
- A developer asks to add mock coverage for an existing ports interface
- A test needs to replace
On(...).Return(...)setup on a hand-rolled struct with generated mock expectations
Placement Convention
Mocks live in the infrastructure layer, beside the concrete implementations:
Interface package (application/ports/) |
Mock output directory (infrastructure/) |
|---|---|
ports/api/btc/ |
infrastructure/api/btc/mocks/ |
ports/api/eth/ |
infrastructure/api/eth/mocks/ |
ports/api/xrp/ |
infrastructure/api/xrp/mocks/ |
ports/file/ |
infrastructure/storage/file/transaction/mocks/ |
More from hiromaily/go-crypto-wallet
shell-scripts
Shell script development workflow. Use when modifying files in scripts/ directory or any *.sh files.
56makefile-update
Makefile development workflow. Use when modifying Makefile or files in make/ directory.
37docs-update
Documentation update workflow. Use when modifying files in docs/ directory or any markdown files (*.md).
34btc-terminology
Critical Bitcoin terminology rules to prevent confusion between bech32m (encoding) and taproot (address type). Use when working on BTC-related code, config files, or shell scripts.
34db-migration
Database schema and migration workflow. Use when modifying database schemas in tools/atlas/ or SQLC queries in tools/sqlc/.
31openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
27