Top 3 Go go-testing Projects
Automatically generate Go test boilerplate from your source code.Project mention: Table-driven tests are overrated. | /r/golang | 2023-01-17
I believe vscode does it using gotests (https://github.com/cweill/gotests), so people can probably use it outside of vscode too.
Test generation for Developers. Generate tests and stubs for your application that actually work!Project mention: 6 AI Tools every developer must try | dev.to | 2023-07-12
Keploy is an open-source, end-to-end (E2E) testing toolkit for developers. It creates test cases and data mocks/stubs by recording API calls, database queries, etc., making releases faster and more reliable. Keploy works by being added as a middleware to your application. It captures and replays all network interaction served to the application from any source. This allows Keploy to generate test cases for all of your API endpoints, including those that are not explicitly tested by your unit tests. This can help you to identify and fix bugs that would otherwise go undetected. Keploy can create data mocks/stubs for your APIs, which can help you to isolate your tests and make them more reliable. It can automatically compare test cases generated from previously collected traffic against updated behaviour of your application, and bring any differences to your attention. This can help you to identify regressions in your production code early on.
Collect and Analyze Billions of Data Points in Real Time. Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.
Some useful functions to simplify and improve testingProject mention: Testing survey | /r/golang | 2022-10-27
The standard Go testing environment is very good, certainly for unit testing. You might want to use some test helper packages to provide some missing features. For instance, table-driven testing where you have a table of test-specific structures providing inputs and expected results which you iterate over, is a good way of organising your tests. One downside is that the test failure will all be reported from the same line and it can be hard to find the failing test. A useful helper to identify the failing test is the ID struct from github.com/nickwells/testhelper.mod/v2/testhelper which if created using the MkID function will show the filename and line of the failing test. This package also offers standardised comparison checks and support for Golden files and lots more.
Go go-testing related posts
What are some of the best open-source go-testing projects in Go? This list will help you: