github.com/stretchr/testify/require.Failf
third-partyThe 8717th most-called third-party function by production calls. Called 210 times across 51 modules; 69 of those run outside tests and generated code.
0% in production calls vs 2026-W37 (0 → 69)
All of github.com/stretchr/testify/require → Docs on pkg.go.dev ↗
- prod calls
- 69
- non-test, non-generated
- all calls
- 210
- total callsites
- modules
- 51
- distinct callers
- in loop
- 36%
- of prod calls
- in tests
- 67%
- 140 calls
- resolved
- 100%
- to a known target
resolution mix
How each call resolves
How each call was attributed. Only resolved kinds, where the target function is known, count toward the ranking. Interface dispatch and unresolved receivers are reported separately and never guessed. Read the taxonomy →
- Package function100%A direct call to an exported package function, resolved by type.
who calls this
Notable callers
Production calls into Failf from notable Go projects. Open one on the map to see what else it hammers.
where it's called
Callsites in the wild
12 representative callsites of 210, prioritizing in-loop and non-test usage. We link to source, never display it.
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
-
go.temporal.io/server @v1.32.0
tests/activity_driver.go:203
in loop - in loop
- in loop
-
vitess.io/vitess @v0.24.3
go/test/endtoend/topotest/utils/utils.go:32
in loop - in loop
- in loop
top callers
The modules that reach for it
The modules that call Failf most in this snapshot.
- github.com/dapr/dapr2512%
- github.com/vitessio/vitess2010%
- vitess.io/vitess2010%
- github.com/ClickHouse/clickhouse-go/v2199%
- github.com/temporalio/temporal136%
siblings
More from github.com/stretchr/testify/require
The other most-called functions in this package. See all →