mockery v3 is GA and includes Moq templates
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 135
- Avg merge
- 11d 6h
- Merged PRs (30d)
- 1
Description
I just released [mockery v3](https://vektra.github.io/mockery/v3.0/)! Users of moq should be able to migrate over to mockery and use the `template: matryer` config parameter.
@breml has already done this and has been a huge help in making this migration smoother for moq users. There likely still exist some caveats and corner cases I have not teased out, so please let me know if you find anything.
After a certain point, I would suggest putting https://github.com/matryer/moq into maintenance-only mode, or even archive it, once we've confirmed that all necessary features have been properly represented in mockery.
Feel free to also read my announcement on my [personal blog site](https://topofmind.dev/blog/2025/04/08/announcing-mockery-v3/) that explains more of the history and intentions of mockery.
CC @matryer @sudo-suhas.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked mockery v3 announcement and the repository's current feature coverage; the issue names no files, tests, or entry points. The work would need to identify remaining moq caveats and confirm feature parity before deciding whether maintenance-only mode or archiving is appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100