Sample
github.com/stretchr/testify 1.11.1: Stop a failed testify assertion from crashing the next line, and know when to use require instead of assert
Verified sample for golang github.com/stretchr/testify 1.11.1: Stop a failed testify assertion from crashing the next line, and know when to use require…
sha256:06e2218bf94b889eb5e1ba6287aa0148d4b894a277afe7b73f5ae6c8c0fdc1aa
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
go 1.26 linux x64 go 1.26 go gomod
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| go 1.26 · linux alpine/x64 · docker ed25519:a2ec939a4c60e243 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1 |
2026-08-14 |
| go 1.26 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1 |
2026-08-18 |
Case
FIX- Goal
- Stop a failed testify assertion from crashing the next line, and know when to use require instead of assert
- Packages
- Symbols
-
- assert.TestingT
- require.TestingT
- require.NotNil
- assert.NotNil
- assert.Equal
- assert.ObjectsAreEqual
- assert.EqualValues
- assert.ElementsMatch
- Environment
- go 1.26
- Created
- 2026-08-14T08:50:06Z
Contract
- 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
Files
- csx.json
- go.mod
- go.sum
- src/probe.go
- test/main.go