Sample
BDD testing suite with Describe, Context, and It using RunSpecs
sha256:6f67659227b93c1b6236a450a333f0e1fee18b970294570213aa34572a18c94a
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
- 1
- Signing keys that built it
- 1
Declared environment
go 1.26 linux 24 · ubuntu · glibc 2.39 x64 go 1.26 go go 1
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| go 1.26 · linux alpine/x64 · docker ed25519:c1973797be207ac4 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · golang@1golang:1.26-alpine@sha256:28d89ee9cc0f… |
2026-08-23 |
Case
HOW- Goal
- BDD testing suite with Describe, Context, and It using RunSpecs
- Packages
- Symbols
-
- Describe
- It
- RunSpecs
- Environment
- go 1.26.6
- Created
- 2026-08-23T17:11:17Z
Contract
- Describe and Context organize test suites hierarchically with isolated state
- It defines executable test specifications with By steps and assertions
- BeforeEach and AfterEach manage test lifecycle initialization and cleanup
- DeferCleanup registers callbacks executed in LIFO order upon test completion
- DescribeTable and Entry execute parameterized table specifications
- RunSpecs executes the test suite against a custom GinkgoTestingT runner
Files
- PROMPT.md
- csx.json
- go.mod
- go.sum
- spec.json
- test/contract.go
Origin Seeder
anonymous