go-testdeep VS versioninfo

And do not forget to use go-testdeep and its JSON operator to test JSON content: :)

TestDeep. I got pretty used to many of the matchers and they simplify my life now.

To see the result on a large repository, I adapted the comments of go-testdeep to fully take advantage of these new features.

Check also go-testdeep → https://goplay.tools/snippet/KgoeGR1bIwT the full featured testing framework... (not related to go-test/deep)

Check go-testdeep using its operators, it is very easy to do table driven tests, see https://goplay.space/#Z91D72aH3Sc for an example

See https://github.com/maxatome/go-testdeep/releases/tag/v1.11.0 for changes.

the 1.10.0 release with many new features including a new SuperSliceOf operator (so now 62 operators!), a relaxed JSON parser, the possibility to ignore unexported struct fields, to target a specific nested field (even private), the enhancement of tdhttp HTTP API tester to check cookies, to use multipart/form-data bodies, and many other magic things…

And of course go-testdeep which colorizes the error reports with simple but accurate diff.

Links: - Github — https://github.com/maxatome/go-testdeep - Home — https://go-testdeep.zetta.rocks/ - Releases — https://github.com/maxatome/go-testdeep/releases - tdhttp the API tester — https://pkg.go.dev/github.com/maxatome/go-testdeep/helpers/tdhttp - tdsuite the testing suite — https://pkg.go.dev/github.com/maxatome/go-testdeep/helpers/tdsuite

Oh, also https://github.com/carlmjohnson/versioninfo . Always need that.

Don’t. It’s obsolete. Just use debug.ReadBuildInfo()

That’s obsolete. See https://github.com/carlmjohnson/versioninfo. Even if it weren’t, Make is an inappropriate tool. Because it is based on file modtimes, it can’t react to git hash changes. You just have rerun the steps every time, at which point Bash is a less awful language.

Go 1.18 updates the debug info to also include the git status of the build. See https://github.com/carlmjohnson/versioninfo

I use this trick in my versioninfo package. Obviously, it can't give you other tags, but most of the time the tag you want to know about is v1.2.3 anyway, and since tags are mutable but the Go sum DB is immutable, this is safer than just saying what tag was on disk at build time.

I subscribed to GH activity for the correspondence friendliness-enhancing library by the author:

https://github.com/carlmjohnson/versioninfo/

The primary motivation curiousity to learn if this becomes "the [best/default] way" folks reach for when leveraging BuildInfo to deliver explicit binary versioning.