ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Test a Passport.js authentication flow in a local test environment while avoiding any calls to external OAuth providers. The test must simulate the provider’s token exchange, user profile retrieval, and session handling without using real production credentials. Constraints To keep the tests deterministic, the OAuth endpoints must be intercepted (e.g.,
Karma proxy configuration When running unit tests that hit external services, the proxies setting in karma.conf.js can redirect network traffic to a mock server. However, the current configuration lacks a mapping for the /api endpoint used by the application under test. Without this mapping, tests that perform HTTP requests to https://api.example.com/resourc
When using RSpec with WebMock to intercept HTTP requests, the library intercepts calls at the library level. This mechanism typically bypasses the actual SSL/TLS handshake, meaning certificate validation logic is never executed. Developers need to verify how the application handles expired certificates, mismatched hostnames, or untrusted CAs. There is curren
When implementing DRY test suites in RSpec, shared examples can be integrated into a spec using either it_behaves_like or include_examples . While both methods allow for the reuse of common expectations, they handle the execution context and documentation output differently. The primary goal is to determine the optimal method for maintaining clean failure tr
Coverage threshold scope in Gleam 0.12 Gleam's gleam test --coverage --threshold flag, added in version 0.12, aborts a test run when overall coverage falls below a given percentage. The documentation does not clearly state whether that percentage is evaluated against the aggregate line coverage of the entire project or against each compiled module individual
Goal: run integration tests against a service mock without ever exposing production credentials on Unix‑like hosts. Constraints: environment variables are universally understood by shells and most client libraries, yet they can leak into child processes and logs unless explicitly scoped. Unix domain sockets give fast, isolated channels but require careful so
When testing Laravel applications that call external APIs, developers often use Http::fake() to stub outbound requests and avoid sending real calls or exposing production credentials. The goal is to confirm that the test suite uses only the credentials defined in .env.testing while Http::fake() is active, ensuring no accidental use of live keys. However, it
I want to exercise Portainer's integration flows (endpoint listing, registry connections, stack deployment) in an isolated test instance without ever touching production secrets. My plan is a fresh portainer-ce container with its own data volume, a throwaway registry configured with dummy credentials via the built-in "Test connection" button, and a limited-s
When writing integration tests that exercise external services, the primary goal is to run those tests without exposing or requiring real production credentials. The Zig language offers std.testing and test blocks that are executed via zig test , but the standard library does not provide a built‑in mocking framework or fixture support to replace external dep
passport
karma
rspec
ruby
gleam
unix
laravel
docker
zig