Exemple

Stop a failed testify assertion from crashing the next line, and know when to use require instead of assert

sha256:06e2218bf94b889eb5e1ba6287aa0148d4b894a277afe7b73f5ae6c8c0fdc1aa

PUBLISHED L3_CONTRACT_PASS MIT-0

Cas

Objectif: Stop a failed testify assertion from crashing the next line, and know when to use require instead of assert FIX
Paquets: github.com/stretchr/testify 1.11.1
Environnement: go 1.26
Créé: 2026-08-14T08:50:06Z

assert a t with only Errorf satisfies assert.TestingT and does not satisfy require.TestingT
assert a failed assert.NotNil returns false, records one failure, and calls FailNow zero times
assert the statement after that failed assert still runs and panics with a runtime nil pointer dereference
assert a failed require.NotNil records the same single failure and calls FailNow exactly once
assert require abandons the body before the dereference, so nothing panics, and deferred cleanup still runs
assert a FailNow that returns instead of calling runtime.Goexit turns require back into assert and the panic returns
assert Equal rejects 1 against int64(1) and prints both types in the message, while EqualValues converts and passes
assert ObjectsAreEqual compares slices by order and calls a nil slice unequal to an empty one
assert the []byte shortcut in ObjectsAreEqual compares equal contents equal but still calls a nil slice unequal to an empty one, even though bytes.Equal calls those equal
assert a named type over []byte never compares equal to a plain []byte in either direction, while still comparing equal to itself
assert ElementsMatch ignores order but counts multiplicity, where Equal does neither

go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-14 · ed25519:a2ec939a4c60e243
· CONTAINER_RUN · compile:SKIPPED · contract:FAIL · load:SKIPPED · resolve:PASS · golang@1 · 2026-08-14 · ed25519:7da3f610facce8bf