Sample
Show that a missing upload path in Rack::Test does not raise a filesystem-style error.
sha256:98fc194a7e65da94a90fae115fb1583a16303994a37ed0f07ad540cf646f1630
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Show that a missing upload path in Rack::Test does not raise a filesystem-style error. HOW
- Packages
- rack-test 2.2.0
- Environment
- ruby
- Created
- 2026-08-16T16:42:53Z
Commonly assumed
Passing a missing file path to `Rack::Test::UploadedFile.new` should raise a filesystem exception such as `Errno::ENOENT`, not a generic runtime error.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert_raises(RuntimeError) { Rack::Test::UploadedFile.new('data/missing.bin') }
- assert_equal('data/missing.bin file does not exist', assert_raises(RuntimeError) { Rack::Test::UploadedFile.new('data/missing.bin') }.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