Sample
Prove that a patch upgrade of ostruct changed the missing-field error message format in OpenStruct#delete_field.
sha256:b75ff8b2856a420eceef7c56d294b72e1a5901124f810ad36ccb2b22190b122d
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Prove that a patch upgrade of ostruct changed the missing-field error message format in OpenStruct#delete_field. HOW
- Packages
- ostruct 0.6.1
- Environment
- ruby
- Created
- 2026-08-16T16:29:19Z
Commonly assumed
A patch upgrade should preserve the style of NameError messages for OpenStruct#delete_field, so missing-field errors should still use backticks.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert Deleting a missing field with OpenStruct#delete_field raises NameError and its message uses single-quoted key syntax ("no field 'key'")
- assert OpenStruct#delete_field does not include backtick characters in the missing-field NameError message
Files
- Gemfile
- NOTES.md
- csx.json
- test/contract.rb
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9