social
go-sqlmock
| social | go-sqlmock | |
|---|---|---|
| 4 | 19 | |
| 487 | 5,837 | |
| 0.2% | 0.9% | |
| 8.3 | 5.4 | |
| 10 days ago | about 1 month ago | |
| PHP | Go | |
| GNU Affero General Public License v3.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.
social
-
Could you set up like your own personal fediverse instance
Fill your boots
-
Finally my NextCloud setup is complete with full working NextCloud Social app ππ
Don't believe me? Check the GitHub: https://github.com/nextcloud/social
-
Alternative implementations
NextCloud Social - Microblogging inside the cloud platform.
- Nextcloud Social
go-sqlmock
- How do you unit-test code that reaches out to the db, without introducing interfaces everywhere?
-
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?
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
- SQL mock driver for Golang to test database interactions
- Can't get a specifc SQL query with pgx to work
-
[HELP] how to test this piece of code?
There is a good lib for db tests https://github.com/DATA-DOG/go-sqlmock
What are some alternatives?
GNU social - GNU social is social communication software for both public and private communications.
gomock - GoMock is a mocking framework for the Go programming language.
wtf - The personal information dashboard for your terminal
go-txdb - Immutable transaction isolated sql driver for golang
wtf - WTF Dial is an example web application written in Go.
mockery - A mock code autogenerator for Go
nextcloud.com - π Our website
gock - HTTP traffic mocking and testing made easy in Go ΰΌΌΚΜΩΝΚΜΰΌ½
friendica-addons - Addons for Friendica. This is a mirror of the repository at git.friendi.ca
minimock - Powerful mock generation tool for Go programming language
esp-v2 - A service proxy that provides API management capabilities using Google Service Infrastructure.
gotests - Automatically generate Go test boilerplate from your source code.