testhelper.mod VS gotests

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.

You can get the testhelper package with

A huge time-saver for me when generating table-driven test boilerplate in Go has been using gotests[0] to generate the template.

If you use VSCode with the Go extension it's already available there as a command "Go: Generate Unit Tests for Function/Package".

[0] https://github.com/cweill/gotests

I believe vscode does it using gotests (https://github.com/cweill/gotests), so people can probably use it outside of vscode too.

What can do this plugin? - Modify struct tags. - Run go get, go mod & go generate commands inside of nvim. - Implement interface by impl. - Generate tests by gotests. - Install required tools for plugin working(by go install).

I was just thinking about some smart solutions. For example generating test plan and fake data by inspecting current changes on the code and db schema. Just like this https://github.com/cweill/gotests but for performance test plans.

Did you encounter gotests when you were doing your research? It's a table test generation tool that generates test code using t.Run(). I do wish it could generate tests using testify, because I frequently end up rewriting the code in the inner loop, but I still use it because it's better than I am about ensuring there's a test for all functions I write.

I use https://github.com/cweill/gotests to generate the test scaffolding.

You can save yourself a minute and generate the test case boilerplate for your with https://github.com/cweill/gotests :)