testcase VS go-mutesting

One of them focuses on time manipulation for testing purposes: - Freeze time to a specific point. - Travel back to a specific time, but allow time to continue moving forward. - Scale time by a given scaling factor will cause the time to move at an accelerated pace. - No dependencies other than the stdlib - Nested calls to timecop.Travel is supported - Works with any regular Go projects

Fault Inject Package Repo URL

If you like test-driven design, check out my testing framework. https://pkg.go.dev/github.com/adamluzsi/testcase https://github.com/adamluzsi/testcase

refs: - https://github.com/adamluzsi/testcase/releases/tag/v0.71.0 - https://github.com/minimaxir/big-list-of-naughty-strings

In the testcase testing framework, I mostly used github.com/stretchr/testify for the assertions, and everywhere where I work with the testing framework. Most of the time, I barely use the full potential of testify, just some basic assertations like Contains and Equal. I decided to ship these basic assertions within the testing framework, so when I don't need heavy lifting with a full-fledged assertion library, I don't need to import one.

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