evans
gomock
Our great sponsors
evans | gomock | |
---|---|---|
11 | 40 | |
4,115 | 9,010 | |
- | - | |
4.8 | 2.5 | |
4 months ago | 10 months 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.
evans
-
Understanding gRPC Concepts, Use Cases & Best Practices
Note: gRPC services can also be tested from CLI using tools like evans-cli. But for that reflection needs (if not enabled the path to the proto file is required) to be enabled in gRPC servers. This compare link shows the way to enable reflection and how to enter into evans-cli repl mode. Post entering repl mode of evans-cli, gRPC services can be tested from CLI itself and the process is described in evans-cli GitHub page.
- Evans: More expressive universal gRPC client
-
Smart way to create gRPC CLI
Do you mean this one https://github.com/ktr0731/evans ?
-
grpcurl-like tool for grpcweb
I use Evans, it supports gRPC and gRPC-web and also supports reflection protocol.
-
Go and gRPC is just so intuitive. Here's a detailed full-stack flow with gRPC-Web, Go and React. Also, there is a medium story focused on explaining how such a setup might boost efficiency and the step-by-step implementation.
https://github.com/ktr0731/evans it's the best cli tool I've ever used
-
Postman-powered testing of Akka Serverless gRPC APIs
Over the holidays, 2021, Postman gifted a fine upgrade to its users: beta support for the gRPC protocol in its API platform. As a Product Manager for Lightbend and helping out on its new gRPC native PaaS for building and running APIs and microservices, I was excited, to say the least. In another, recent blog post, I mentioned my desire to leverage UI test-and-try tools for APIs (my time in the REST API world of Mashery and PubNub was the source of such desire). In that same post though, I noted the lack of several important gRPC features, like server reflection and more robust import capabilities, as blockers; hence, my deep dive, in that post, into the CLI tool, Evans.
-
gRPC test-and-try with Akka Serverless and Evans
And who am I kidding? I'm a CLI-type person. Which is why I was super excited to stumble about Evans. Within minutes, I had gone from installation to trying out TLS-secured APIs and microservices running in the cloud on Lightbend's new serverless offering.
-
Set Up Grpc Web Server With AWS
If everything is set up correctly, you should now be able to use evans to access your web server at the load balancer url or even the url for your ec2 instance directly e.g.
-
Setting Up a gRPC Protobuf Server With Tonic
After running the server with cargo run, I needed a way to test that the server works. I had heard of an interesting tool called evans, so I decided to use this. It took me a while to figure out the right parameters to query the server, especially because tonic doesn't seem to support gRPC reflection right now, and there are few examples out there.
-
Go, RabbitMQ and gRPC Clean Architecture microservice 💫👋
For testing gRPC we can use evans and need add reflection:
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.
What are some alternatives?
grpc-web - gRPC for Web Clients
mockery - A mock code autogenerator for Go
grpcui - An interactive web UI for gRPC, along the lines of postman
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
bloomrpc - Former GUI client for gRPC services. No longer maintained.
pgx - PostgreSQL driver and toolkit for Go
grpcurl - Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
sqlx - general purpose extensions to golang's database/sql
Go-gRPC-RabbitMQ-microservice - Go gRPC RabbitMQ email microservice
counterfeiter - A tool for generating self-contained, type-safe test doubles in go
tonic - A native gRPC client & server implementation with async/await support.
monkey - Monkey patching in Go