-
It would be nice, that testify could handle `os.Exit(1)` like `panic("blub")` with https://godoc.org/github.com/stretchr/testify/assert#Assertions.Panics
-
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Open
These updates have all …
-
As discussed in https://github.com/insomniacslk/dhcp/pull/71 , it is worth considering moving away from assertion libraries like the one we use, `github.com/stretchr/testify`.
-
### What version of Go are you using (`go version`)?
$ go version
go version devel go1.21-993707a9d6 Tue May 30 20:19:54 2023 +0000 linux/arm64
### What did you do?
```go
package main
…
-
We use `TODO` and `FIXME` by default, but we should let people specify their own code tags too.
This means people could use it for more than just TODOs:
- showing all mentions of `@mazondo` in the co…
-
## Description
I am testing a workflow, so if one test step fails, the test should not proceed. For example, if the login fails, there is no point in adding items to the cart. I am using assert…
-
We recently observed tough to read diffs produced by testify on assertion failures on structs when the structs contain nested `time.Time` objects.
I have created this repo with this testfile that d…
-
### What happened?
Policy
```yaml
apiVersion: kuma.io/v1alpha1
kind: MeshMetric
metadata:
name: ...
namespace: kuma-system
spec:
targetRef:
kind: MeshService
name: ...
de…
tolwi updated
3 weeks ago
-
While reviewing dependencies on some other poject, i found this one was somewhat suffering from a recurrent update policy which is good security practice in general.
a `go get -u` reveals the follo…
-
We need tests for each API endpoint. Thoughts on frameworks on this?