moq
dockertest
moq | dockertest | |
---|---|---|
16 | 48 | |
1,771 | 3,978 | |
- | 1.1% | |
3.6 | 3.0 | |
7 days ago | 9 days 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.
moq
- vektra/mockery has fully released the "packages" feature! This blog explains what it is and how it works.
- Why elixir over Golang
-
Is gomock still maintained and recommended?
``` https://github.com/matryer/moq
-
How do you write/generate mocks for testing?
Currently trying out https://github.com/matryer/moq for the first time, and quite positive so far. Haven't pushed it enough yet to give a real opinion.
-
gomock giving me a hard time
I like moq much better than gomock. Much simpler and easier to work with.
-
how to mock DBs
Just replaced mockery generated mocks with https://github.com/matryer/moq Alot cleaner imo at least for me
- Testify Mocking conundrums
-
Can someone please comment on this mock example from Jon Calhoun's post on DDD?
btw, you can avoid making such mocks manually by using https://github.com/matryer/moq, which will generate such mocking code for you
-
How do you control behaviour in mocked interface ?
I like the way of matryer/moq a lot. Basically, it generates a func for each of the methods of an interface, therefore the behaviour is clear to everyone without too much abstraction.
-
What mocking framework do you prefer?
This one is easy to use, simple, powerful and idiomatic https://github.com/matryer/moq
dockertest
-
Testcontainers
I am using https://github.com/ory/dockertest for tests, specifically for databases. Is there any advantage to use Testcontainers?
-
Level UP your RDBMS Productivity in GO
Now, let's run the tests. For this purpose, we are going to use dockertest, but test containers is also a good solution.
-
Golang testing using docker services via dockertest
During my path learning go so far I have come across some amazing libraries and utilites, one of my favourite for integration testing is dockertest.
-
How to start a Go project in 2023
Things I can't live without in a new Go project in no particular order:
- https://github.com/golangci/golangci-lint - meta-linter
- https://goreleaser.com - automate release workflows
- https://magefile.org - build tool that can version your tools
- https://github.com/ory/dockertest/v3 - run containers for e2e testing
- https://github.com/ecordell/optgen - generate functional options
- https://golang.org/x/tools/cmd/stringer - generate String()
- https://mvdan.cc/gofumpt - stricter gofmt
- https://github.com/stretchr/testify - test assertion library
- https://github.com/rs/zerolog - logging
- https://github.com/spf13/cobra - CLI framework
FWIW, I just lifted all the tools we use for https://github.com/authzed/spicedb
We've also written some custom linters that might be useful for other folks: https://github.com/authzed/spicedb/tree/main/tools/analyzers
-
Beginner-friendly API made with Go following hexagonal architecture.
I've used dockertest a bunch and it is really amazing.
-
How to unit test your database interactions with Docker
Reminds me of https://github.com/ory/dockertest
-
When to mock and what to mock in a Web API?
If your project is relatively simple and you can get away with recreating your scenarios against a real mock database and run other related services locally. It would be good to setup docker containers for your test scripts and write e2e tests. I believe e2e tests are harder but more useful in understanding/reasoning how users are impacted.
-
Don't Mock the Database
Just a heads up, the repository in your comment is invalid, the correct link is https://github.com/ory/dockertest
-
Mocking database calls without a library?
Don't mock. Use https://github.com/ory/dockertest to actually run tests against a dockerized DB.
-
Different SQL drivers for test and production
Use a library like ory/dockertest to spin up a test database for integration tests. It's easy to use, and tests are still fast. It'll take a minute to download the mysql docker image the first time. But, once it's been downloaded, starting the db, running migrations, and running the tests is still pretty quick.
What are some alternatives?
gomock - GoMock is a mocking framework for the Go programming language.
testcontainers-go - Testcontainers for Go is a Go package that makes it simple to create and clean up container-based dependencies for automated integration/smoke tests. The clean, easy-to-use API enables developers to programmatically define containers that should be run as part of a test and clean up those resources when the test is done.
mockery - A mock code autogenerator for Go
fake-gcs-server - Google Cloud Storage emulator & testing library.
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
mockaroo - Mock-A-🦘 (mock-aa-roo) a comprehensive HTTP/HTTPS interface mocking tool for all your development and testing needs!
NSubstitute - A friendly substitute for .NET mocking libraries.
venom - 🐍 Manage and run your integration tests with efficiency - Venom run executors (script, HTTP Request, web, imap, etc... ) and assertions
counterfeiter - A tool for generating self-contained, type-safe test doubles in go
steampipe - Zero-ETL, infinite possibilities. Live query APIs, code & more with SQL. No DB required.
GORM - The fantastic ORM library for Golang, aims to be developer friendly
go-sqlmock - Sql mock driver for golang to test database interactions