testfixtures VS go-mutesting

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.

To solve the problem we will use testfixtures. Create a folders fixtures и fixtures/storage and put a file users.yaml inside:

A lot of good suggestions here, I would also take a look at go-testfixtures which allows you to create some simple yaml-based fixture data to use with unit testing. It's quick and easy, but yes can get unwieldy the more you add.

I built an alternative to Make written in Go that is simpler to use and cross-platform: https://taskfile.dev/

Also, a library to write tests with databases for Go: https://github.com/go-testfixtures/testfixtures

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.

I think this is the most up to date mutation testing library for Go: https://github.com/zimmski/go-mutesting

Mutesting has been my "new favorite thing" for a while. I hope that mutation scores replace flawed metrics like statement coverage in the future. Sqlite's test suite[0] is probably my favorite example of its power.

[0]: https://www.sqlite.org/testing.html

I personally use go-mutesting[1] with my Go projects, which is a bit basic but gets the job done. Mutmut might be worth investigating for when I work with Python.

[1]: https://github.com/zimmski/go-mutesting