DemandHunt Demand signals from global communities
EN
Dev Tools & Micro-SaaS Stack Exchange · 2026-10-13

Hand-written Postman regression suites can't keep up with API changes

手写的 Postman 回归测试集永远追不上接口变化

At a glance · 30-second read
  • WhoStack Exchange · 2026-10-13 · 1 replies
  • The askHand-written Postman regression suites can't keep up with API changes
  • The openingRecord real traffic to auto-generate regression tests with downstream mock snapshots and derived assertions, CI-friendly. Open-source core plus a paid team tier.

What was actually said

“I maintain a set of REST microservices (Go and Node.js, in Docker on Linux) and our API regression suite is mostly hand-written Postman collections. Keeping them updated takes too much time, and our mocks for downstream services drift from real behaviour.”

— Stack Exchange · 2026-10-13 · softwarerecs.stackexchange.com/questions/95686/open-…

Background and pain

The pain

Manual suites are expensive to maintain and mocks drift from real downstream behaviour: green CI no longer means nothing broke.

A buildable angle

The opening

Record real traffic to auto-generate regression tests with downstream mock snapshots and derived assertions, CI-friendly. Open-source core plus a paid team tier.

How to validate it

  1. Read the whole thread and note the recurring scenarios — repetition is the density of the need.
  2. Search existing tools around "api testing / regression" and check which single step they actually cover.
  3. Put up a one-line landing page, share it back to Stack Exchange, and see whether anyone asks about pricing.

Existing options

Hoverfly, WireMock, VCR

From the thread · top comments

Three tools come up for "record real traffic → tests + dependency mocks". Only two of them cover your full list. 1. Keploy (closest fit, Apache-2.0) Tests from traffic: keploy record captures API calls and the outbound dependency calls, then keploy test replays them as tests with the dependencies mocked. Dependency mocks: the README lists Postgres, MySQL, MongoDB, Redis, Kafka/RabbitMQ and external HTTP. No instrumentation: it captures at the network layer with eBPF, so no SDK or code changes are needed and the language doesn't matter. On Linux that means it needs root. The mock quickstart in

— Ayush Nautiyal · ▲ 0
Open the source thread

More threads on this pain

Related opportunities