November 11, 2025
Testing tape or tech trap?
Show HN: Tusk Drift – Open-source tool for automating API tests
Record-and-replay testing tool drops — fans cheer, skeptics cry “brittle!”
TLDR: Tusk Drift records real app calls and replays them as tests to catch bugs without hitting the outside world. The community is torn: fans love the idea, skeptics ask how it avoids brittle results, handles changing data and expiring tokens, and how it differs from tools like mitmproxy and vcrpy.
Tusk Drift just hit “Show HN,” promising a big red replay button for server tests: it records real app traffic and plays it back to catch bugs, without calling the outside world again. That’s the pitch. The crowd? Split, spicy, and very online. One camp is excited: “Finally, someone attacking this pain,” says chrisweekly, while others immediately poke holes. sg_gabriel shows up like the designated party pooper: what happens when your app changes? Do tests become “brittle snapshot tests” and start failing because the timestamp changed? People want answers on normalizing chaos like time, IDs, and expiring login tokens (JWTs), with zmj asking how those don’t go stale mid-test.
Then the comparison game begins. imiric drops the classic “What does this do that I can’t do with mitmproxy?” while scientism calls it Python’s vcrpy but for Node. Cue memes about “cassette tapes” and devs haunted by flaky tests. Under the hood, Tusk Drift supports a laundry list of popular tools and databases, it’s open-source (Apache 2.0), and has a CLI plus an SDK to get rolling fast. But the real drama is whether recorded tests can stay trustworthy as your app evolves. Is this testing magic—or just replaying yesterday’s problems? The thread’s vibe: hopeful, skeptical, and full of “prove it” energy.
Key Points
- •Tusk Drift records real-world API calls and replays them as deterministic tests using the Tusk CLI.
- •During replay, all outbound requests are intercepted and served with recorded data to avoid side effects.
- •Comprehensive documentation includes initialization, environment variables, quick start, and troubleshooting guides.
- •Supports multiple packages and versions, including HTTP/HTTPS, gRPC, PostgreSQL, Firestore, MySQL, Redis, GraphQL, Prisma, JWT, and JWKS RSA.
- •Installation involves setting up the CLI, installing the Node.js SDK, initializing it in the service, and running the first test; the project is open-source under Apache License 2.0.