ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal Develop a test harness for a Jaeger client that can be run in CI or local environments without using real production credentials. Constraints and Uncertainty The Jaeger client library expects an authentication token or basic auth header when sending spans to a secured collector. Using production credentials in tests is forbidden by policy, yet the colle
Goal Determine whether Racket's testing ecosystem should supply a built‑in mock connection for racket/db 's connect procedure so that integration tests can run without real database credentials. Constraints and uncertainty The connect function raises an authentication‑required error when username or password are omitted, as documented in racket/db . Teams cu
The goal is to run Ansible playbooks in check mode (--check) inside a CI pipeline to validate changes without applying them, thereby avoiding the need to expose production credentials. However, check mode does not guarantee that every module behaves as a pure read‑only operation; some modules may still attempt to connect to managed nodes, gather facts, or ca
RSpec alert throttling to suppress duplicate failure messages The goal is to configure RSpec so that identical alert messages (e.g., the same failure output for a shared example) are emitted only a limited number of times during a test run, reducing console noise without suppressing distinct failures. Currently RSpec provides formatters and the RSpec::Core::
Deciding on a mocking strategy for a growing RSpec suite Our team is standardizing how we isolate collaborators in unit tests, and we keep hitting the same unresolved decision: when to use allow , when to use expect , and when spies are the better fit. The suite mixes all three styles inconsistently, and reviewers disagree on what each test is actually promi
Goal: Determine whether to use Moleculer’s FakeTransporter or a local test broker with dummy credentials when writing integration tests that must avoid production secrets while still validating transporter‑specific behavior. Constraint: FakeTransporter runs in‑process, eliminating network latency and external dependencies, but it bypasses transporter middlew
I need to run a Grunt task that executes a shell command (e.g., a curl request) to verify an integration with a third‑party API. To avoid exposing real secrets, I want to supply test‑only credentials through grunt‑env and have grunt‑shell use those values in its command template. I am unsure how to isolate the environment so that the shell task does not inad
Goal Confirm whether Jasmine automatically converts an unhandled promise rejection inside an async test into a spec failure, and identify the conditions that influence this behavior across releases. Constraints & Uncertainty Jasmine 3.6+ claims to treat rejected promises or thrown errors in async functions as failures, but earlier releases lack native as
Context A Fortran codebase calls an external REST API that requires production credentials. The goal is to run integration tests in CI without those credentials, using test doubles for the HTTP client. Two documented patterns exist: C-preprocessor conditional compilation ( #ifdef TEST ) and Fortran 2003 polymorphism with abstract interfaces. Constraint The p
jaegertracing
racket
ansible
rspec
ruby
moleculer
grunt
jasmine