gomock
moq
Our great sponsors
gomock | moq | |
---|---|---|
40 | 20 | |
9,010 | 5,693 | |
- | 1.7% | |
2.5 | 7.5 | |
10 months ago | 11 days ago | |
Go | C# | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gomock
- Maintainership of Go’s official gomock repo has been transferred to Uber.
- Uber Now Maintains Gomock
-
Google Stopped Maintaining GoMock
The commit mentions this rather sad thread: https://github.com/golang/mock/pull/627#issuecomment-1605169...
-
Tools besides Go for a newbie
IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here
-
When to mock and what to mock in a Web API?
Normally I like to generate everything with Mockgen and test it using table driven test.
-
Is gomock still maintained and recommended?
Looking at gomock's commit history, it seems like there hasn't been much activity on the project in a couple of years. I'm wondering if this is the case of software being mostly done and just in maintenance mode, or if gomock is falling behind. The reason I fear for the latter is there are still issues being opened up that don't seem to be engaged very much.
-
Want to know if this is a valid approach
Yeah, that would work just fine. Nevertheless, as your business logic gets more complicated, you will want to test more scenarios and mocks will get complicated fast. In these cases tools like gomock really shine and make your life easier. I understand that this is a just-for-fun project, but it's never too early to experiment with a popular solution, especially if you plan on using Go professionally in the future.
-
Go API Project Set-Up
Unit tests are leveraged to test individual units of code. As such it is not recommended for a developer to scaffold entire dependencies for the sake of testing a single object. Due to the way Go's specific implementations work, I've learned over time to declare interfaces for a lot of the structs that I use in Go. Interfaces not only define a contract for which struct-based implementations should adhere, but they also provide a mechanism for which struct methods can be mocked. While I've experimented with the mock package in testify, I've come to prefer the mock functionality which is provided by mockgen.
-
Comprehensive Guide to Testing in Go
gomock can also be great for testing when used sparingly. Mocking out one or two calls is great, anymore than that and it becomes exponentially harder to reason about
-
Google's internal Go style guide
Where we do use mocks, we primarily use GoMock.
moq
- Warum wird so wenig Open-Source-Software in Unternehmen genutzt?
- The release notes for Moq 4.20.2 seem to suggest, that this version does not contain this dubious mechanism [obfuscated DLL collecting commit emails], although it may be temporary, as the reason is that it breaks builds on MacOS.
-
.NET developers alert: Moq NuGET package exfiltrates user emails from git
Moq’s prior version, 4.18.4, free of the exfiltration behavior, accounts for 6,765,006 downloads in the past six weeks, demonstrating the potential blast radius of privacy breach if a developer hadn’t noticed the issue and raised it with the community.
-
Ask HN: Benefits to Keeping Packages Updated?
In light of the Moq issue yesterday[0] I'm interested to understand why the consensus seems to be so in favor of keeping packages up-to-date in software.
The common explanation I see is it "keeps you up to date with security and bug fixes".
But in practice this seems to just involve most orgs mandating Dependabot and mindlessly updating every dependency when a new version becomes available. (Yes in an ideal world you code review every change in every dependency, but... I mean, let's be real here. Just take the update frequency of the AWS SDK packages in isolation, very few orgs are actually doing this)
As a maintainer of an open source library I know most releases are a crapshoot, they're just as likely to contain new bugs and flaws as they are to fix old ones.
So staying up-to-date seems to open up codebases to far greater risks than outdated dependencies:
1) Zero days, a new package launches with some critical security flaw that isn't going to get noticed for some time.
2) Supply chain attacks, old packages are generally immutable. Therefore most supply chains attacks seem to involve take-overs of existing package (name)s by disgruntled or new hostile 'maintainers'. The new versions are far more at risk.
3) New bugs, the dirty truth of OSS is most work is done by unpaid people with little time or ability to focus. Most software isn't formally verified. New updates are a risk.
In addition the old version is a known quantity. Unless you know absolutely the version you are running is compromised (log4j, OpenSSL) what benefits does updating actually bring? The default presumption that version number goes up is better seems like yet more security/compliance cargo cult behavior.
What am I missing here?
[0] https://github.com/moq/moq/issues/1374
- Moq: Warnings with Latest Version from SponsorLink
- Moq SponsorLink and supporting OSS more broadly
-
Popular open source project Moq criticized for quietly collecting data
NSubstitute is good, I used it at a previous job.
I've favored Moq in the past because I think there are a couple of things it makes a bit easier or is a bit less opinionated about, but NSub is perfectly cromulent as well.
Someone posted a quick guide to migrating a bunch of it easily in one of the issues in the Moq repo discussing this whole mess: https://github.com/moq/moq/issues/1374#issuecomment-16712411...
-
The Moq-gate: You Either Die a Hero...
Moq was is a popular .NET mocking library that has accumulated over 475.7 million downloads as of now.
-
Does Moq extract and send my email to the cloud via SponsorLink?
Going by reports in the releated Github issue Moq does not let users opt out of this privacy-invading data collection: https://github.com/moq/moq/issues/1372
This is sad. Moq was my favorite mocking framework in .net. I will not be using it moving forward and if I had any projects using it I'd rip it out ASAP.
- Moq – Privacy issues with SponsorLink, starting from version 4.20
What are some alternatives?
mockery - A mock code autogenerator for Go
NSubstitute - A friendly substitute for .NET mocking libraries.
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
Fluent Assertions - A very extensive set of extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style unit tests. Targets .NET Framework 4.7, as well as .NET Core 2.1, .NET Core 3.0, .NET 6, .NET Standard 2.0 and 2.1. Supports the unit test frameworks MSTest2, NUnit3, XUnit2, MSpec, and NSpec3.
pgx - PostgreSQL driver and toolkit for Go
sqlx - general purpose extensions to golang's database/sql
AutoFixture - AutoFixture is an open source library for .NET designed to minimize the 'Arrange' phase of your unit tests in order to maximize maintainability. Its primary goal is to allow developers to focus on what is being tested rather than how to setup the test scenario, by making it easier to create object graphs containing test data.
counterfeiter - A tool for generating self-contained, type-safe test doubles in go
cell-cms - CMS leve, self-contained e prático de utilizar! Feito por desenvolvedores e para desenvolvedores!
monkey - Monkey patching in Go
Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.