SaaSHub helps you find the best software and product alternatives Learn more →
Top 23 Go Testing Framework Projects
-
Como herramientas te recomiendo: FastJson https://github.com/valyala/fastjson : Si necesitas leer jsons Testify https://github.com/stretchr/testify : Para mockear y testear
-
Project mention: Is there a more detailed test coverage report than go test -cover? | reddit.com/r/golang | 2022-08-01
IIRC you can use http://goconvey.co/ just for the reports
-
InfluxDB
Build time-series-based applications quickly and at scale.. InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises.
-
Project mention: ginkgo integration with jira/elasticsearch/webex/slack | reddit.com/r/golang | 2023-01-17
If you are using Ginkgo for your e2e, this library might of help.
-
Project mention: Visualizing Diffs The Myers difference algorithm | news.ycombinator.com | 2022-11-03
This made me think of a couple other interesting things:
1. you can change which algorithm is used in git diff as multiple are supported
https://luppeng.wordpress.com/2020/10/10/when-to-use-each-of...
2. Google has an edit graph implementation in Go in the cmp package
https://github.com/google/go-cmp/blob/master/cmp/internal/di...
-
Since the project also uses Postgres, Redis, and AMQP, we also write integration tests. A docker compose file is there to stack up the test suite, and before each test, the tables, the keys, and the queues are reset. We don't try to aim to test for all the cases but usually all the controllers are covered. I personally would prefer to write more test cases between multiple micro services (e2e?) using something like Gauge but these integration tests are kind of enough.
-
found it thank you. For pointing that out
-
I also use BDD (Gherkin with godog in particular) to verify and document the expected behaviour of a product from an end user's perspective when needed. I usually do this when the product also contains untested code that I have no control over when I'm working on a problem - this gives me peace of mind over something I can't control while doubling as documentation.
-
SonarQube
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
-
Project mention: Quick tip: Easy test assertions with Go generics | reddit.com/r/golang | 2022-04-03
-
Project mention: The Go libraries that never failed us: 22 libraries you need to know | reddit.com/r/golang | 2022-12-13
-
gnomock
Test your code without writing mocks with ephemeral Docker containers 📦 Setup popular services with just a couple lines of code ⏱️ No bash, no yaml, only code 💻
-
Mocking the http client using recorded responses; for example using dnaeon/go-vcr
-
I'm the author of https://github.com/go-testfixtures/testfixtures, a library written to make it easier to write tests with a real database and test data. You might want to use it together with docker-compose, for example.
-
-
-
-
-
-
hi, is there a way to integrate this command https://github.com/zimmski/go-mutesting with neovim, and to run it on every buffer save.
-
embedded-postgres
Run a real Postgres database locally on Linux, OSX or Windows as part of another Go application or test
This is down to nuance, but all databases are "file based" as they all write to files. But most of them require a separate process with lock coordination to get away from writer lock delays and ensure ACID, which includes Postgresql. Calling any version of pgl "embedded" is confusing because I see that being used to describe pgl databases which are run in a localhost mode with a single reader/writer client. Regardless, those still require a postgres process and access it over IP. For simplicity, if one uses a database by touching its files directly from the process accessing the database, then it's "embedded"; but then again I guess that semantic ship has sailed: https://github.com/fergusstrange/embedded-postgres so the point may be moot.
-
-
testza
Full-featured test framework for Go! Assertions, fuzzing, input testing, output capturing, and much more! 🍕
Project mention: Testza: A full-featured go testing framework with developer-friendly output | reddit.com/r/golang | 2022-04-01 -
gotest.tools
A collection of packages to augment the go testing package and support common patterns.
Assertion libraries that people seem to love: - testify (my favorite) - go-cmp is a more barebones library - gotest.tools -- I have never used this but some swear by it
-
go-testdeep
Extremely flexible golang deep comparison, extends the go testing package, tests HTTP APIs and provides tests suite
And do not forget to use go-testdeep and its JSON operator to test JSON content: :)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Go Testing Frameworks related posts
- Golang, GraphQL y Postgress
- What's your favourite part of unit testing?
- ginkgo integration with jira/elasticsearch/webex/slack
- Introdução aos testes unitários em Go
- Working with JSON in Go: A Comprehensive Guide
- Is that a unit test a.k.a how do you test your API endpoints?
- Learning Go and I don't like some features, maybe it's me?
-
A note from our sponsor - #<SponsorshipServiceOld:0x00007fea5b98e7c8>
www.saashub.com | 4 Feb 2023
Index
What are some of the best open-source Testing Framework projects in Go? This list will help you:
Project | Stars | |
---|---|---|
1 | Testify | 18,763 |
2 | GoConvey | 7,588 |
3 | ginkgo | 6,817 |
4 | go-cmp | 3,330 |
5 | Gauge | 2,782 |
6 | Looking for Maintainer | 2,055 |
7 | godog | 1,884 |
8 | gomega | 1,825 |
9 | is | 1,516 |
10 | gnomock | 1,038 |
11 | go-vcr | 984 |
12 | testfixtures | 900 |
13 | goblin | 875 |
14 | baloo | 750 |
15 | GoAws | 704 |
16 | gocheck | 666 |
17 | goc | 617 |
18 | go-mutesting | 569 |
19 | embedded-postgres | 518 |
20 | gofight | 428 |
21 | testza | 410 |
22 | gotest.tools | 391 |
23 | go-testdeep | 340 |