httpmock
gomock
httpmock | gomock | |
---|---|---|
6 | 41 | |
1,947 | 9,010 | |
- | - | |
5.2 | 2.5 | |
21 days ago | over 1 year ago | |
Go | Go | |
MIT License | Apache License 2.0 |
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.
httpmock
- Integration Tests in Go with Cucumber, Testcontainers, and HTTPMock
- Golang rest-api testing
- [Rant] Sa Isi Bage Microserviciile in C*R
-
Integration tests with Go and testcontainers
We will use httpmock for this purpose. Inside function setupSuite(), where we created useCase and provided nil as a billingClient now we will pass mocked http client:
-
Best practices around mocking interfaces from external packages
Alternatively, you could use an http mock library like https://github.com/jarcoal/httpmock, and override the urls the RealClient calls with a mock response in your tests.
-
best way to mock/unit test http.Client?
To mock an API: https://github.com/jarcoal/httpmock to use when your code calls external APIs so you don't want your tests call the real API. No need to create an interface as you do.
gomock
- Go mock
- 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
What are some alternatives?
gock - HTTP traffic mocking and testing made easy in Go ༼ʘ̚ل͜ʘ̚༽
mockery - A mock code autogenerator for Go
hoverfly - Lightweight service virtualization/ API simulation / API mocking tool for developers and testers
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
mockit - Library that make mocking of Go functions/methods easy
pgx - PostgreSQL driver and toolkit for Go
httpexpect - End-to-end HTTP and REST API testing for Go.
counterfeiter - A tool for generating self-contained, type-safe test doubles in go
minimock - Powerful mock generation tool for Go programming language
sqlx - general purpose extensions to golang's database/sql
go-vcr - Record and replay your HTTP interactions for fast, deterministic and accurate tests
go-sqlmock - Sql mock driver for golang to test database interactions