The MustCreate Pattern for Go Tests

I think in these cases, I would either ignore the error (`username, _ := ...`) or write a simple `assert(t, err == nil)` that makes the `if` check just one line. Then, fuzz `NewUsername` separately to handle the cases where the requested username could be invalid and those errors matter. But hey, decent application…

Simpler, but with `panic` ("with a value I know is valid"): ```go func Must[T any](t T, err error) T { if err != nil { panic(err) } return t } ``` Then it is a normal function call: `user := Must(NewUsername("john"))` https://go.dev/play/p/XEx083CU9EJ --- If you are really allergic to panic: ```go func Must[V any](v…

Thanks for reading! I similarly don't think I'd object to yours in the wild, but I do find it less expressive. The advantage of `MustCreate` is that it communicates to the reader that this is logic that's unrelated to the system under test. If you do `assert(t, err == nil)`, then it looks like any other assertion in…