autogold VS backoff

I use autogold for my tests now, and I use the -update feature already twice. That's really handy.

https://github.com/hexops/autogold - generate and update test result (go test -update .)

this way, you can switch around framework easily without changing the business logic, and all business logic easily testable without thinking about serialization at all (just matching the input struct and output struct, for example using https://github.com/hexops/autogold)

prefer these two tools: https://github.com/maxbrunsfeld/counterfeiter and https://github.com/hexops/autogold

There is a small issue with string-pointers and inline-updating autogold.Want calls, can you have a look? https://github.com/hexops/autogold/issues/4

Why this instead of https://github.com/avast/retry-go or https://github.com/cenkalti/backoff ?

What about https://github.com/cenkalti/backoff?

In addition to the ones you mentioned, I also always use: + sqlc - Compile SQL to type-safe code + gqlgen - generate GraphQL server from schema + oapi-codegen - Go client and server boilerplate from OpenAPI 3 specifications + pester - Go http calls with retries and backoff + backoff - exponential backoff algorithm in Go

May I suggest directions to improve? - add option for exponential or linear backoff - stop early on non-retriable errors Example: https://pkg.go.dev/github.com/cenkalti/backoff/v4 (do not know about its author, just a package I've been using).

I have used https://github.com/cenkalti/backoff a few years ago and I don't know if it's the best candidate at this point but it's worth to consider in combination with or as an alternative to x/time/rate if you are going that route.