Gleam integration tests with large API IDs: gleeunit suite behaves differently across Erlang and JavaScript targets
I'm designing an integration test suite for a Gleam service that talks to an external API. Following the documented gleam test workflow with gleeunit, the plan is to inject configuration (base URL, token) via environment variables and pass a fake HTTP client into the application code so tests return canned gleam/http responses instead of hitting production.
gleam