Polly.js – Record, replay, and stub HTTP interactions
Looks well done (it uses unicode art, so it must be amazing) but I have a fundamental distrust/dislike of record/replay frameworks...just seems like you're papering over an inherently bad testing approach.<p>E.g. sure, when replays work, they're great, but:<p>a) you have to do a manual recording to create them the first time (which means manually setting up test data in production that is just-right for your test case)<p>b) you have to manually re-record when they fail (and again means you have manually go back and restore the test data in production that is just-right for your test case...and odds are you weren't the one who originally recorded this test, so good luck guessing exactly what that was).<p>In both cases, you've accepted that you can't easily setup specific, isolated test data in your upstream system, and are really just doing "slightly faster manual testing".<p>So, IMO, you should focus on solving the core issue: the uncontrollable upstream system.<p>Or, if you can't, decouple all of your automated tests from it fully, and just accept that cross-system tests against a datasource you can't control is not a fun/good way to write more than a handful of tests (e.g. ~5 smoke tests are fine, but ~100s of record/replay tests for minute boundary cases sounds terrible).