webmock

There are lots of variations depending upon your use case. For unit testing and CI you may want mock objects that are implemented in the same language as your code. Google search for "mock object <language>". That's where you'll find Mockito (Java) or Mocha Spy (NodeJS) or Testify (golang). This list never ends. Specifically for unit testing of a UI, you may want your browser driver to handle this, ex: Cypress has built-in support for mock AJAX endpoints. https://docs.cypress.io/guides/guides/stubs-spies-and-clocks... If you want an endpoint you can call, Postman has a feature for this, there are several others like this in the comments (JSON Server, mmock, mountebank, etc.). https://learning.postman.com/docs/postman/mock-servers/setti... If you need to capture traffic, check out goreplay or mitmproxy: https://github.com/buger/goreplay ht

I follow. I should preface it by saying I'm working with a team of about 10 developers. For every developer to have to the software working on their local machine, it's a burden. Our unit/functional tests run clean when SSL is stubbed out from client requests. We use webmock (https://github.com/bblimke/webmock) to mock 3rd party integrations. Upon deploy to staging, integration tests (Selenium) sweep through. Our monitoring software ensures the app and its 3rd party services are responding to those integration points. So yeah, developing by yourself, it's ok-ish. Though I still prefer having infrastructure be predictable. Mocking the SSL configuration through a reverse proxy feels brittle to me...it usually isn't how production is configured. I guess another way of putting it -- I'd rather not inspect to make sure the app and its componen