tag
testing
4 posts.
-
Pointing HTTPS_PROXY at port 1 only tests the fast failure
ECONNREFUSED returns in milliseconds, so a proxy-at-port-1 offline test never runs your timeout path. Test DNS failure and black holes too, with a time budget.
-
Your load test measured the watchdog, not the server
A bash wait-plus-backgrounded-curl harness reported 85s and two hangs for a server whose real 4-concurrent latency was 6.5s. Per-request timeouts found it.
-
Your commit message claimed a call path that doesn't exist
A tool fan went from 770ms wall to 633ms against 1398ms of work. The commit said it fixed the chat path. The changed code had two callers, both CLI-only.
-
Your isolated test lab isn't isolated: 3 rows, 8 daemons
My failure-injection harness wrote to the live database, health-checked a stranger's process, and leaked 8 daemons. Three bugs in the test, none in the code.