Sample
faraday 2.11.0: Test Faraday code against stubbed HTTP with no network, and work out which parts of Faraday 2 still need an extra gem
Verified sample for gem faraday 2.11.0: Test Faraday code against stubbed HTTP with no network, and work out which parts of Faraday 2 still need an extra…
sha256:46eed9d91592cb5df8548ed6884a818eba294fbab879f42106d919a145b91d8a
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
ruby 3 linux x64 ruby 3 ruby bundler
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| ruby 3 · linux alpine/x64 · docker ed25519:a2ec939a4c60e243 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · gem@1 |
2026-08-14 |
| ruby 3 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · gem@1 |
2026-08-18 |
Case
HOW- Goal
- Test Faraday code against stubbed HTTP with no network, and work out which parts of Faraday 2 still need an extra gem
- Packages
- Symbols
-
- Faraday::Adapter::Test
- Faraday::Adapter::Test::Stubs
- Faraday::Response::Json
- Faraday::Response::RaiseError
- Faraday::ServerError
- Faraday::ResourceNotFound
- Environment
- ruby 3
- Created
- 2026-08-14T09:45:11Z
Contract
- assert a Faraday::Adapter::Test stub matching path and query serves the whole connection with no socket
- assert a query the stub declared has to match exactly, while a parameter it did not name is ignored and a stub with no query matches every query
- assert an unmatched request raises Faraday::Adapter::Test::Stubs::NotFound naming the URL
- assert the host from the connection url_prefix reaches the matcher, so a stub written for another host does not match
- assert a 500 without raise_error is only a response, and with raise_error is a Faraday::ServerError
- assert middleware order decides whether the raised error carries a parsed or a raw body
- assert raise_error maps a 404 to Faraday::ResourceNotFound
- assert a JSON body stays a String until the json middleware is added, and then only on a JSON content type
- assert verify_stubbed_calls raises on a stub that went unused, while a consumed stub still answers a repeat call
- assert the test adapter and the json and raise_error middleware ship inside faraday itself
- assert the default net_http adapter is a separate gem, an unregistered adapter fails at lookup, and the default adapter really opens a socket
- assert no json gem is resolved into the bundle, because faraday 2.11 parses with the json Ruby ships
Files
- Gemfile
- Gemfile.lock
- csx.json
- src/api.rb
- test/contract.rb