monkey
DISCONTINUED
go-sqlmock
Our great sponsors
monkey | go-sqlmock | |
---|---|---|
14 | 19 | |
2,370 | 5,786 | |
- | 1.8% | |
0.0 | 4.7 | |
almost 4 years ago | 2 months ago | |
Go | Go | |
GNU General Public License v3.0 or later | 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.
monkey
- Many reasons to always read the LICENSE
-
Library for monkey-patching functions
This person did not read the license of the original library https://github.com/bouk/monkey/blob/master/LICENSE.md
-
Alternative for Monkey patching
I am a new gopher. I was looking into the Monkey Patching module and it is archived now. I was wondering if there is an alternative for that.
-
Why go plugin addresses do not load with go binary
Here is an example of this in Go - but as he says, don't actually do this. https://github.com/bouk/monkey
-
is there an easy (python like way) to do mocks?
I discovered this lib a few days ago. https://github.com/bouk/monkey it allows you to monkey patch entire functions, replacing them by whatever you want. Perfect for mocking. It's simple to use. The program is hard patching the code using assembly to replace the function address at runtime. You should not use this lib out of your tests since it's absolutely not safe. It's only compatible with linux and windows. But it works great!
- Monkey Patching in Go (2015)
- I do not give anyone permissions to use this tool for any purpose. Don’t use it. I’m not interested in changing this license. Please don’t ask.
-
Project includes a dependancy that has a license that forbids its use
From the explaining blog post [0]
> If you’re not interested in how it works and you just want to do monkey patching, then you can find the library here.
Also
> Wrapping it up in a nice library
> I took the above code and put it in an easy to use library. It supports 32 bit, reversing patches, and patching instance methods. I wrote a couple of examples and put those in the README.
Then in the README[1]:
> Make sure you read the notes at the bottom of the README if you intend to use this library.
Either the author is confused or has decided that he doesn't want to maintain an hack. Anyway license is pretty clear.
There was an HN thread[2] when it was released.
[0] https://bou.ke/blog/monkey-patching-in-go/
"This is as unsafe as it sounds and I don't recommend anyone do it outside of a testing environment."
[1]: https://github.com/bouk/monkey#i-thought-that-monkeypatching...
go-sqlmock
-
Creating an API using Go and sqlc
For that, I used the lib go-sqlmock. So, for example, the following snippet is part of the person/service_test.go file:
-
Using SQLC in project how do I mock database Calls with it for unit testing?
I’m writing a post about it! I will post soon, but you can use https://github.com/DATA-DOG/go-sqlmock to mock your database calls
It's not the right call IMO to skip mocking the database connection to achieve 100% test coverage. How your app will behave in failure scenarios that are impossible to imitate during integration tests is part of the software contract. If your choice is to panic, or return an error, document that by testing that behavior. If another dev, or future you inadvertently breaks the contract, the test suite will fail. That's what you want. For unit tests against your database you should be using either go-sqlmock if testing against database/sql or pgxmock if testing against pgx. That being said, the points raised elsewhere in this thread regarding unit tests potentially hiding edge cases in terms of how an actual database will interact with your application that are not reflective of your understanding when writing mocks are 100% valid. You should do both. Unit test your app and write integration tests as well. On my team, we run integration tests using docker-compose.
- What is the coolest Go open source projects you have seen?
- How to mock database calls
-
Can you set expectations for SQL transaction using Testify?
I use Sqlmock for that purpose
-
Mocking database queries - ask for opinion
I use https://github.com/DATA-DOG/go-sqlmock for unit testing my data layer code. Most of the times, these tests help me to find errors whenever I do a refactor on the data layer, so I consider it a good safety net
-
I share my authentication server.
Continuous Integration - Testify, sqlmock, Mockery, Github Actions
-
[HELP] Testing SQL queries and functions that use SQL queries in Golang.
For testing DB queries I use https://github.com/DATA-DOG/go-sqlmock for unit tests. I then have a separate integration test suite that runs against all our services using Docker.
What are some alternatives?
gomock - GoMock is a mocking framework for the Go programming language.
go-txdb - Immutable transaction isolated sql driver for golang
mockery - A mock code autogenerator for Go
gock - HTTP traffic mocking and testing made easy in Go ༼ʘ̚ل͜ʘ̚༽
minimock - Powerful mock generation tool for Go programming language
gotests - Automatically generate Go test boilerplate from your source code.
tidb-lite - Using tidb-lite to create a TiDB server with mocktikv mode in your application or unit test.
realize - Realize is the #1 Golang Task Runner which enhance your workflow by automating the most common tasks and using the best performing Golang live reloading.
Mmock - Mmock is an HTTP mocking application for testing and fast prototyping
rust-by-example - Learn Rust with examples (Live code editor included)